Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Chris Spanellis 29 posts 140 karma points
    Apr 22, 2019 @ 16:19
    Chris Spanellis
    0

    Bug in RebuildContentDbCacheLocked not paging correctly

    Please see below. We have 5,523 content nodes, and only 5,000 would get built/loaded into the cache properly. This of course caused a LOT of headache for us before we realized what was going on.
    enter image description here

    For the fix, I first ToArray'ed the descendants, and then just increased processed by descendants length:

    var descendants = _documentRepository
        .GetPage(query, pageIndex++, groupSize, out total, null, Ordering.By("Path"))
        .ToArray();
    ...
    processed += descendants.Length;
    

    Can we get a patch for this ASAP?!

  • Stephen 767 posts 2268 karma points c-trib
    Apr 23, 2019 @ 09:06
    Stephen
    100

    Oh my, confirmed. Is issue #5315, discuss on the tracker.

    Thanks for reporting - and nice detective work. Must have been... awful #h5yr

  • Chris Spanellis 29 posts 140 karma points
    Apr 23, 2019 @ 16:51
    Chris Spanellis
    0

    Thanks Stephen. What's the best way to update the NuGet reference in our project? Create a forked version, and then reference that?

  • Stephen 767 posts 2268 karma points c-trib
    Apr 23, 2019 @ 17:03
    Stephen
    0

    The fix has been merged into the v8/8.0 branch, so it will be part of 8.0.2 that is to be released "soon".

    If you want it now, you can get branch v8/8.0 and build your own packages.

    Alternatively, our Build Pipeline on Azure DevOps produces build of v8/8.0. The build with the fix is build 20416 and the top-right Artifacts button lets you download the corresponding NuGet packages.

Please Sign in or register to post replies

Write your reply to:

Draft