Posted March 18, 2023
McFirson: Even running gogcli by itself, different versions, for a single game, without GUI, fails.
This is the error output when I try to add "140" to the manifest by using either method (it's the first game in my list):
140
[manifest writer] Generating/Updating manifest for 3 games
[manifest writer] Got all info on game with id 1096313866. 2 games left to process
[manifest writer] Got all info on game with id 1440426004. 1 games left to process
[sdk] getDownloadFileInfo(downloadPath=/downloads/earth_2140_trilogy/4443) -> body retrieval error: unexpected EOF. Will retry.
And it goes on like this. After closing the terminal by hand small window pops up with message "Retrieval failed! Error 3".
What does "Earth 2140 Trilogy" have to do with "140"?
...
If you want, I can direct this to Magnitus thread, as it doesn't seem an issue with GUI.
I regularly use gogcli for my backups and it works fine. However, I don't often use the full manifest generation to validate all the games. I believe I have the specific game that trips you up, so I'll give it a try this weekend. This is the error output when I try to add "140" to the manifest by using either method (it's the first game in my list):
140
[manifest writer] Generating/Updating manifest for 3 games
[manifest writer] Got all info on game with id 1096313866. 2 games left to process
[manifest writer] Got all info on game with id 1440426004. 1 games left to process
[sdk] getDownloadFileInfo(downloadPath=/downloads/earth_2140_trilogy/4443) -> body retrieval error: unexpected EOF. Will retry.
And it goes on like this. After closing the terminal by hand small window pops up with message "Retrieval failed! Error 3".
What does "Earth 2140 Trilogy" have to do with "140"?
...
If you want, I can direct this to Magnitus thread, as it doesn't seem an issue with GUI.
Otherwise, concerning things that may pop up:
Occasionally, it can happen that gog has a bad file (the unintentional kind of bad file that you need to open a support ticket and get them to fix). When that happens, if its an important file (ex: an installer), I'll open up a support ticket with GOG, but if the file is not important (ex: a patch file), I'll usually just add an exception for it in my manifest and gogcli will ignore it.
Besides the above, GOG's file metadata endpoints (used to retrieve the expected checksum of the file) can sometimes be bad (it used to be a lot worse, I think they've improved it) and from what you describe, I believe that is what is happening there. When that happens, gogcli will retry about 4 times or so and then if it still fails, it will circumvent the metadata endpoint by simply doing a mock download of the file and computing the checksum itself.
If the later situation happens, there might be a delay (especially for a larger file, downloading it may take some time depending on the file's size and the speed of your internet connection) while the file is downloaded and the checksum is computed. when that happens, after the delay, you'll get a message informing you that the longer workaround method has been used for the file.
Do note that the above workaround solution that been implemented only in more recent versions of gogcli so if your version lag behinds, then you'll just get an error as there won't be any workarounds for you. Given my limited personal time, I can only commit to fixing problems in the latest release.
Post edited March 18, 2023 by Magnitus