[resolved] Bug Beta 1: Resources not being indexed
Four free resources (by Sproul) were downloaded and I let a fifth resource (LLS:GODWILLSPROUL) download whilst indexing was underway (at 53%). It was succesfully discovered, treated "as installed" and did not interrupt the indexing, BUT it was not indexed (I know it didn't index because I tried searching for the word "Adam" and got zero results).
This indexer log shows what happened to all five resources. I lost the Logos.log but have notes on the timing of events.
The reindex command did not work for LLS:GODWILLSPROUL
Dave
===
Windows 11 & Android 13
Comments
-
Can you post the LogosIndexer.log file from after entering the reindex command?
Andrew Batishko | Logos software developer
0 -
Also, can you tell me if the following file exists: E:\Beta\Logos5\Data\ohq13iv1.hru\ResourceManager\Resources\GODWILLSPROUL.logos4
Andrew Batishko | Logos software developer
0 -
Can you post the LogosIndexer.log file from after entering the reindex command?
There isn't one! See log file after consecutive reindex commands
Dave
===Windows 11 & Android 13
0 -
Also, can you tell me if the following file exists: E:\Beta\Logos5\Data\ohq13iv1.hru\ResourceManager\Resources\GODWILLSPROUL.logos4
It sure is (resource can be opened and can be searched as mentioned above).
Dave
===Windows 11 & Android 13
0 -
Deleted GODWILLSPROUL and it was successfully indexed after Logos re-downloaded it.
Dave
===Windows 11 & Android 13
0 -
I believe I've got this fixed up. It should be available in beta 3.
Andrew Batishko | Logos software developer
0 -
I believe I've got this fixed up. It should be available in beta 3.
Want more logs? I bought a book, let it download and start indexing. While that was going on I purchased a second book. After it downloaded it didn't index. I was checking to see what would happen since the previous behavior (on mac) caused the indexing to restart.
0 -
Want more logs? I bought a book, let it download and start indexing. While that was going on I purchased a second book. After it downloaded it didn't index. I was checking to see what would happen since the previous behavior (on mac) caused the indexing to restart.
Not unless it happens again in beta 3.
Andrew Batishko | Logos software developer
0 -
Andrew, what should we do about resources that are already afflicted? Choosing reindex resourcename doesn't work for these resources. Should we hide them, then unhide them, or will they magically get indexed with beta 3?
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
I deleted the resource(s) and it was indexed after the download.
Dave
===Windows 11 & Android 13
0 -
Andrew, what should we do about resources that are already afflicted? Choosing reindex resourcename doesn't work for these resources. Should we hide them, then unhide them, or will they magically get indexed with beta 3?
Deleting the resource and doing an "update resources" to get it to download is best. I wouldn't suggest hide/unhide, since there is still a known problem with unhiding resources.
Andrew Batishko | Logos software developer
0 -
-
I wouldn't suggest hide/unhide, since there is still a known problem with unhiding resources.
Oops. That's what I did. Do I need to fix something?
[:D]
Option 1: Wait until this is fixed in beta 3 or 4.
Option 2: I haven't tested this, but you might be able to unhide the resource and then exit the application and delete the Updates.db file from the UpdateManager folder.
Andrew Batishko | Logos software developer
0 -
I believe I've got this fixed up. It should be available in beta 3.
This should be fixed in 6.3 Beta 3.
0 -
I tested this again in Beta 3, and it does appear to be working correctly.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
I believe I've got this fixed up. It should be available in beta 3.
This should be fixed in 6.3 Beta 3.
It appears to be fixed!
Dave
===Windows 11 & Android 13
0
