Odd behavior in 22.0 beta 1?
I thought this was strange, so I am posting it in case others see something similar.
My system was current on 10.1, resources updated - I got 4 resources into my library yesterday, and indexing was complete. Around dinner time, after being away from my desk most of the day, I noticed on the forums that beta 1 was out. So I checked my Verbum/Mac install (which I left open on my laptop), and sure enough it had updated and was waiting for a restart to finish. I restarted, it came back up, everything was fine. I did just a little work, and went away to do other things.
Late in the evening I came back - and I noticed the indexer was on 43% - odd - what downloaded? I looked in my library, and I checked the list "resources downloaded in the last day" (or whatever that says) under the blue circle, and nothing appears to have downloaded! I didn't think much about it, and went to bed.
This morning, I come to my desk. Verbum is still open on my laptop. I notice the indexer is on 54% - I think "Whoa - is it stuck? 43% to 54% in 8 hours or so is a problem!" But then I notice that it goes from 54% to being finished in less than 5 minutes, so it was not stuck. So what is going on?
It seems to me one of two things was happening:
1) At least twice, the indexer has decided to run, for no apparent reason. Maybe it ran more times thru the night?
2) The indexer ran once, was REAL SLOW over night (43% -> 54%), then got unstuck and finished.
There could be other scenarios. Is there some indexing needed with the change to the new numbering system?
Anyway - here are my logs - maybe some explanation shows uo there? Thanks!
Comments
-
I had a dataset update when I downloaded the Beta.
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
0 -
Don Awalt said:
I notice the indexer is on 54% - I think "Whoa - is it stuck? 43% to 54% in 8 hours or so is a problem!" But then I notice that it goes from 54% to being finished in less than 5 minutes, so it was not stuck. So what is going on?
It seems to me one of two things was happening:
You have to be quick, and the logs supplied have over-written the logs of interest.
I noticed some indexing after updating to Verbum 22.0 Beta 1 and captured most of it before being overwritten. 103 resources were reindexed (no download) and it was easy to confirm that I have exactly 103 Bibles in my Library. The log states "Forcing reindexing for 103 resources.", so Faithlife have wanted this to happen for some reason.
Dave
===Windows 11 & Android 13
0 -
Thanks Dave. Everything has seemed normal since then.
0 -
Dave Hooton said:
Faithlife have wanted this to happen for some reason.
I believe my dataset update had to do with Pericopes.
“The trouble is that everyone talks about reforming others and no one thinks about reforming himself.” St. Peter of Alcántara
0 -
SineNomine said:Dave Hooton said:
Faithlife have wanted this to happen for some reason.
I believe my dataset update had to do with Pericopes.
That happened after the forced re-index of my bibles (and probably yours), so its indexing over-wrote the log for the bible re-index.
Dave
===Windows 11 & Android 13
0
