Failed to download binary (Flank bitrise step)
artjedrzejczak opened this issue · 2 comments
Describe the bug
For some time (2-3 weeks) our builds using Flank bitrise step fail due to:
Failed to download binary, error: Get "https://objects.githubusercontent.com/github-production-release-asset-2e65be/84221974/4fb17ff6-cbb3-4e8c-a1ac-6077e5286e23?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20230809%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20230809T022352Z&X-Amz-Expires=300&X-Amz-Signature=5ae18bbed62cbe9624333698a8203d5fe61bcfa81f3695d9400172c1fac83f50&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=84221974&response-content-disposition=attachment%3B%20filename%3Dflank.jar&response-content-type=application%2Foctet-stream": read tcp 10.0.0.59:53662->185.199.108.133:443: read: connection reset by peer
It doesn't happen all the time, but every 3-4 build has this problem. We're using latest version of Flank
I'm not familiar with bitrise. Is there an associated stack trace in addition to the error?
Based on the error alone, it seems like something on the GitHub side is resetting the client connection when the build is pulling down flank.jar from GitHub? Is it possible that there's some rate limit getting hit?
I'm not sure this is something Flank can address given that the string Failed to download binary, error: appears to be in the bitrise step itself. That indicates that the error is occurring before getting to any code that is part of Flank.
You may have better support filing this issue in the bitrise step repository.
Thanks for the extra info @adamvduke -- I've opened a ticket on Bitrise's side of things.