notatallshaw-gts opened a new pull request, #31073:
URL: https://github.com/apache/airflow/pull/31073

   This implemented a retry mechanism to the hvac client as the libraries 
[documentation 
suggests](https://hvac.readthedocs.io/en/stable/advanced_usage.html#retrying-failed-requests).
   
   I am providing this due to a real-world case of an HTTP Connection Error 
causing a task to fail to start, after investigating I found the hvac 
documentation suggested adding this retry process.
   
   Due to the docker version I have access to and the minimum requirements of 
Airflow dev tooling I hit limitations in the MyPy pre-commits and running the 
test suite, but I believe this PR should pass all tests.
   
   Let me know if you need any additional work and/or changes to the PR to be 
able to review and/or land.
   
   Finally, someone else submitted a similar PR but it is failing due import 
errors and they have not updated the PR since it was created three weeks ago: 
https://github.com/apache/airflow/pull/30628
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code changes, an Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+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 a 
newsfragment file, named `{pr_number}.significant.rst` or 
`{issue_number}.significant.rst`, in 
[newsfragments](https://github.com/apache/airflow/tree/main/newsfragments).
   


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to