Revert remote-log upload failure warnings from #66571#68371
Merged
Conversation
…pache#66571)" This reverts commit ef87426. The remote-log upload warnings fired for every task on installs without remote logging configured (a missing handler is the default, not a failure) and were emitted through a dedicated "airflow.logging.remote" logger that only reaches worker stdout, not the task logs operators actually read. The whole change is withdrawn rather than patched.
1 task
ashb
approved these changes
Jun 11, 2026
imrichardwu
pushed a commit
to imrichardwu/airflow
that referenced
this pull request
Jun 16, 2026
…pache#66571)" (apache#68371) This reverts commit ef87426. The remote-log upload warnings fired for every task on installs without remote logging configured (a missing handler is the default, not a failure) and were emitted through a dedicated "airflow.logging.remote" logger that only reaches worker stdout, not the task logs operators actually read. The whole change is withdrawn rather than patched.
dingo4dev
pushed a commit
to dingo4dev/airflow
that referenced
this pull request
Jun 16, 2026
…pache#66571)" (apache#68371) This reverts commit ef87426. The remote-log upload warnings fired for every task on installs without remote logging configured (a missing handler is the default, not a failure) and were emitted through a dedicated "airflow.logging.remote" logger that only reaches worker stdout, not the task logs operators actually read. The whole change is withdrawn rather than patched.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reverts the remote-log upload failure warnings added in #66571.
The structured warnings turned out to be both noisy and low-visibility:
configured — a missing remote handler is the default, not a failure.
airflow.logging.remoteloggerthat only reaches worker stdout, not the task logs operators actually
read in the UI.
I explored a more targeted fix (silencing the no-handler case and routing
genuine failures through the task's own logger so they surface in task
logs), but it added more complexity than this defense-in-depth was worth.
Withdrawing the change entirely is the cleanest path for now; we can
revisit surfacing real remote-upload failures later with a design that
doesn't fire on the common no-remote-logging case.
Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines