potiuk opened a new pull request #13431: URL: https://github.com/apache/airflow/pull/13431
Curl has a sophisticated back-off mechanism when trying to connect and it causes sometimes that it hangs for a very long time when first few attempts to connect failed with a 'soft' error. Similarly, when curl starts transfer after connecting but the other party hanged, the client curl call might hang as well. This causes various problems for example sometimes waitig for images in the ci build gets cancelled because curl command to check for image fails - example: https://github.com/apache/airflow/pull/13413/checks?check_run_id=1635401914 This change adds appropriate timeouts to all curl commands we use in CI/manual operations. In many cases we implemented retry so the effect will be that those cases will stop happening but even in no-retry case, failing curl is better than hangs. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
