[resolved] BUG: Resources are Ready to be downloaded
Downloaded Beta 2 and the Yellow triangle telling me restart disappeared. Downloaded 32 resource updates and its back. The ribbon asking me to restart remained but I was able to close that.
Comments
-
Can you post your log files? Also, can you click on the icon and post a screenshot of the popup that appears?
Andrew Batishko | Logos software developer
0 -
When I originally downloaded the updates they downloaded when I gave permission, library was prepared, and then the indexer ran for a few minutes.
When I restarted to generate a log, the yellow triangle remained and rather than the click to restart command it showed my library was indexing again and went away after a minute or so.
0 -
I think this is operating normally. It's hard to tell for certain since I don't have the logs from the previous run, but it looks like the LCV resource was open when the original download took place. This prevented that resource from being updated, and triggered the prompt to restart. Restarting installed the updated resource, and triggered the indexer. When that finished, the icon went away.
Andrew Batishko | Logos software developer
0 -
It's hard to tell for certain since I don't have the logs from the previous run, but it looks like the LCV resource was open when the original download took place. This prevented that resource from being updated, and triggered the prompt to restart.
I'd prefer a notification in that case, asking me for permission to close the resource so it can be updated in-situ. Or, I'd expect Logos to simply silently wait for the resource or app to be closed, then update it. I can see no point in asking for an app restart.
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 -
Mark Barnes said:
It's hard to tell for certain since I don't have the logs from the previous run, but it looks like the LCV resource was open when the original download took place. This prevented that resource from being updated, and triggered the prompt to restart.
I'd prefer a notification in that case, asking me for permission to close the resource so it can be updated in-situ. Or, I'd expect Logos to simply silently wait for the resource or app to be closed, then update it. I can see no point in asking for an app restart.
We haven't yet settled on how we want to handle this issue. The current implementation is a kind of a first pass at the idea. We've thought about a prompt to reload the layout or trying discovery again when the resource closes. At this point we were concerned about potential problems with being unable to close a resource (see past problems with rebuilding PBBs, but even worse since some resource types are tied to panels in much more complicated ways than PBBs), so it seemed better to make it clear to the user that something was out of date, but a restart would fix it.
Andrew Batishko | Logos software developer
0
