BUG in Library resource count

If I just click on the library icon to get the drop down, I get one answer:
Yet if I drag the Library icon to a column, I get a different answer (this one is correct):
To correct the first one, search on anything, even "Test" - then close out the search, it is correct.
Comments
-
Strange - but fascinating!
I can reproduce what you are describing - with Logos 9.0 SR-2 on MacOS
But after "clearing the problem" and trying again the first option then shows correct results.
The discrepancy on my system - 7 resources - is close to the number of resources that have been updated recently (8 on Friday). I'm just wondering if the first mode is using a non-updated value for the library count which searching for resources and then clearing the search string causes to be updated.
Have you added about 150 resources recently?
0 -
-
Graham Criddle said:
I can reproduce what you are describing - with Logos 9.0 SR-2 on MacOS
But after "clearing the problem" and trying again the first option then shows correct results.
The discrepancy on my system - 7 resources - is close to the number of resources that have been updated recently (8 on Friday). I'm just wondering if the first mode is using a non-updated value for the library count which searching for resources and then clearing the search string causes to be updated.
I saw the same on Verbum 9.1 Beta 3 on Win 10 yesterday - and it was exactly the 9 resources difference that had recently been added. Maybe the pop-up library - in the interest of speed - uses a cached (set of) count number(s) for the library whereas the tab and the window really count it - and someone messed around with the update of those cached numbers?
Have joy in the Lord!
0 -
Thanks for the report. I've created a case to investigate this problem.
Andrew Batishko | Logos software developer
0 -
Thanks Andrew
0 -
Sorry to not reply right away, yes Graham I did probably download about 150 resources very recently, I bought one of the Logos 9 resource packs. I do agree that it seems tied to a recent update of resources, NB.Mick's theory of a caching issue may be the prize. It would also explain why some people might not be able to readily reproduce the bug.
I actually saw this at least as far back as Verbum 8, I don't remember if it goes earlier - I just never remembered to post it.
0