Adjust log message header for expandable sources#66570
Merged
Merged
Conversation
jscheffl
added
type:bug-fix
ashb
approved these changes
May 8, 2026
jscheffl
force-pushed
the
bugfix/adjust-log-message-header
branch
from
798d8c7 to
4536eb7
Compare
jscheffl
requested review from
amoghrajesh,
bugraoz93,
gopidesupavan and
potiuk
as code owners
jscheffl
force-pushed
the
bugfix/adjust-log-message-header
branch
from
4536eb7 to
6a5595e
Compare
jscheffl
requested review from
bbovenzi,
choo121600,
dheerajturaga,
guan404ming,
hussein-awala,
o-nikolas,
pierrejeambrun,
ryanahamilton,
shahar1,
shubhamraj-git and
vatsrahul1001
as code owners
jscheffl
added
full tests needed
jscheffl
force-pushed
the
bugfix/adjust-log-message-header
branch
from
171ee68 to
cecb9d9
Compare
jscheffl
added
the
backport-to-v3-2-test
Contributor
Author
|
Added label too late, backport in #66653 |
potiuk
pushed a commit
that referenced
this pull request
May 10, 2026
…#66653) * [v3-2-test] Adjust log message header for expandable sources (#66570) * Adjust log message header for expandable sources * Fix tests * Fix tests * Fix react tests * Fix backcompat tests with old Airflow versions (cherry picked from commit 8c88254) Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com> * Fix UI test for log grabbing * Fix breeze output static checks
jason810496
pushed a commit
to jason810496/airflow
that referenced
this pull request
May 11, 2026
* Adjust log message header for expandable sources * Fix tests * Fix tests * Fix react tests * Fix backcompat tests with old Airflow versions
vatsrahul1001
pushed a commit
that referenced
this pull request
May 20, 2026
…#66653) * [v3-2-test] Adjust log message header for expandable sources (#66570) * Adjust log message header for expandable sources * Fix tests * Fix tests * Fix react tests * Fix backcompat tests with old Airflow versions (cherry picked from commit 8c88254) Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com> * Fix UI test for log grabbing * Fix breeze output static checks
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
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.
Inspired by PR @ashb in #66037 I am also bothered by the log source details. In our case this sometimes also contains HTTP errors of the endpoint e.g. Edge Worker not reachable to an internal Blob Storage URL which users attempt to open and then report errors. Comments already state the details might distract/confuse users but the kwargs are getting into the group and actually the log group is empty. So totally use-less.
With this PR the actual log source is hidden in the log group now, so exceptions from loading log files are not confusing users, looks like this now:
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.