Posted October 17, 2023
nightstrike_gog: You could probably reduce what gets logged (or make it an option). I don't think it's entirely useful to have so many updates of the download progress for example.
Kalanyr: It's extremely useful for the console output because it lets people know that stuff is happening but it's likely true that the frequency could be cut way down for the logs. Another question, is there a way to checkpoint a forceverify? Or clear all previously verified status so the normal verify can start over? In my case, I moved my repository to a new cloud location, and I'd like to reverify it cloud-side, but my session time is limited, and so I need to keep restarting.
EDIT: Followup question. What does the script do during a download operation between printing out the directory and printing out all the "pass" lines? In the aforementioned cloud setup, the first time through after starting the VM session, there's a large delay processing 1500 passes before downloading for instance 4 updates. If I run it again, it's as fast as running locally. I'm curious what I can do to speed it up. I tried for example stat'ing each file (ls -la */*), but that didn't improve performance. Thoughts?
Post edited October 17, 2023 by nightstrike_gog