search

GitFiend / Support

Public repo for GitFiend questions and issues
118 stars 7 forks source link

Downloads timing out/failing #166

Closed priahoud closed 1 year ago

priahoud commented 1 year ago

There seems to be an issue with the Download-Server when downloading new Releases of GitFiend. The automatic Update-PRs over at Flathub are constantly failing to download current AppImages and are therefore failing to be auto-built and auto-published.

Some of the failing PRs: https://github.com/flathub/com.gitfiend.GitFiend/pull/4 https://github.com/flathub/com.gitfiend.GitFiend/pull/5 https://github.com/flathub/com.gitfiend.GitFiend/pull/6 https://github.com/flathub/com.gitfiend.GitFiend/pull/7 https://github.com/flathub/com.gitfiend.GitFiend/pull/8

Click the "Details" link to the right of the failed builds to see the buildbot errors. They are all failing with a 503 error similar to this one: ERROR src.manifest: Failed to check extra-data gitfiend/GitFiend.AppImage with HTMLChecker: Error downloading upstream source: 503, message='backend read error', url=URL('https://gitfiend.com/resources/GitFiend-0.41.4.AppImage')

Often, but not always, I get the same behaviour when I try to download via browser or wget.

priahoud commented 1 year ago

Looked a bit further into this and found references to the 503 "backend read error" in the Fastly CDN documentation, which you seem to use on your Website. They suggest benchmarking your backend response times and then increasing your backend timeout settings accordingly.

Maybe this is the problem here?

GitFiend commented 1 year ago

From my end I've noticed that downloads can be very slow to start, but haven't had a failure. I think this is mostly after a recent deploy and gets better. The website is a static website using firebase hosting. Firebase apparently does use Fastly, but that and any controls are hidden from me.

priahoud commented 1 year ago

Ok. Seems like there is no issue to resolve then. I asked the Flathub guys if something could be done about the timeouts and unfortunately, I got no answer. Fortunately, though, I got some tips to retrigger the failed automatic pull requests, which I will do for the time being. Thanks for looking into this!