fix: change the decorated order of _get_ssl_context_cached
#57401
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Lee-W
added
the
all versions
Lee-W
changed the title
_get_ssl_context_cached
potiuk
approved these changes
Oct 28, 2025
Member
|
Nice! |
potiuk
added
the
backport-to-v3-1-test
Member
|
The tests for 3.13 passed. Merging. |
github-actions bot
pushed a commit
that referenced
this pull request
Oct 28, 2025
(cherry picked from commit 04c30dc) Co-authored-by: Wei Lee <weilee.rx@gmail.com>
Backport successfully created: v3-1-test
|
potiuk
pushed a commit
that referenced
this pull request
Oct 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
The test cases in #57334 won't pass in 3.13 with the following error.
What
Make
_get_ssl_context_cacheda static method asclsis not accessed and change the order of@lru_cacheand@staticmethod(main issue of the error)^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.