[v3-0-test] Fix remote logging connection availability in Task SDK supervisor (#54679) #54720
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
…pervisor (#54679) Using connections stored in the Airflow Metadata for Remote logging was partially fixed in 3.0.4, but the connection was only set/put-in-scope when the logger was created before task startup. However for blob stores (i.e. S3 or WASB) that is a no-op, and we needed the connection when we try to upload too. (cherry picked from commit b340e8c) Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>
|
Related Documentation No published documentation to review for changes on this repository. How did I do? Any feedback? |
This was referenced Aug 22, 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.
Using connections stored in the Airflow Metadata for Remote logging was partially fixed
in 3.0.4, but the connection was only set/put-in-scope when the logger was created before
task startup. However for blob stores (i.e. S3 or WASB) that is a no-op, and we needed the
connection when we try to upload too.
(cherry picked from commit b340e8c)
Co-authored-by: Rahul Vats 43964496+vatsrahul1001@users.noreply.github.com