Conversation
|
Wow, that must be a slow connection - but a 5min timeout seems rather excessive and will slow down the entire process if a server is unresponsive. Would a 1min timeout also work for you? |
|
It indeed is sluggish, it's around 2 Mb/s.
I'm having a hard time even with 5 min for especially large packages. If the
server is unresponsie, won't Appstream crash anyway? So I'm failing to
understand why this would be a problem, but I'm just running `process bionic`
for what it's worth and could well be missing the bigger picture. If you see a
downside, feel free to close the merge request and I'll build it myself with a
large timeout.
|
|
No, the timeout exists specifically because in the past, bad upstream systems could cause the generator to hang forever - and we never want a bad upstream to stall the entire run. 5min still feels crazy slow for a timeout here, depending on how large the distro is that you are building for, your data generation must take forever in download times! |
|
I built the snap with an outrageous timeout and appstream is indeed hung for about 6 h. So let me indeed close this. I'll look for a different way to go about things and instead of trying to get the output from the horse's mouth, I'll rather try to come up with a "sample output" from Appstream in my local testing environment. Thank you for your help! |
|
Oh, it's good to know that the snap works! :-) You can just run it on a PPA with very few packages, I am using a small local Debian repo for testing purposes. |
2 participants
For a poor man's Internet connection, Appstream will bail out when downloading large debs:
It will thereby crash with