Posted December 15, 2017
Kalanyr: Hmmm. I just did a full manifest update / download (of missing stuff) / verify. And fortunately(?) I had 200 GB to download.
timppu: A lot of GOG installers (that I also downloaded) had a changelog saying something like: "A maintenance update. No game files were changed.".
Yet, the installer size might be quite different from the earlier one (usually bigger) etc, so not sure what exactly was maintained in those cases. At least it was not only about changing the installer filenames (versioning) to the new format.
Oh well, what can you do...
Kalanyr: The problem with hanging due to GOG stopping sending data is fixed. The issue with threads deciding to randomly go AWOL is distinctly not (this is a problem that existed in the original build too). There's no error message of any kind , the threads just disappear and are marked as dead so the section terminates properly, it's like they try and get stuff from the work pool but it's empty even while they are in the middle of downloading (so I guess there's a fall through error path I'm missing somewhere ?). It looks like it's stopping in mid download then requesting more work then flubbing that too, since 2 or 3 AWOL threads (unsure since one thread seems to have come back right at the end by my log) have stopped 11 items downloading*.
timppu: Yeah I've noticed that too, at least lately. I normally have only two threads (esp. as I often run two gogrepo instances in separate windows (because my GOG collection is divided into two), downloading in both at the same time), and sometimes I notice that towards the end only one thread may be downloading, even though I know there are still several files to be downloaded. Also a couple of times I've noticed that the download has been "finished" prematurely (the overall download count hasn't yet reached 0), and running download command again downloads the rest. Is this related to this same problem, e.g. that missing stuff is from the download thread(s) that got stuck earlier?