[v3-3-test] Highlight user-code frames in task log tracebacks (#70294)#70375
Merged
Conversation
In an error traceback the frame that actually failed is usually in the user's DAG code, but it sits visually indistinguishable among the framework frames from installed packages. Emphasising user-code frames and muting installed-package frames lets users find where the error originates at a glance. (cherry picked from commit 4e65210) Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
1 task
pierrejeambrun
approved these changes
Jul 24, 2026
pierrejeambrun
marked this pull request as ready for review
July 24, 2026 09:36
pierrejeambrun
requested review from
bbovenzi,
choo121600,
guan404ming,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
July 24, 2026 09:36
Contributor
Author
|
Hi maintainer, this PR was merged without a milestone set.
|
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
1 participant
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.
In an error traceback the frame that actually failed is usually in the user's DAG code, but it sits visually indistinguishable among the framework frames from installed packages. Emphasising user-code frames and muting installed-package frames lets users find where the error originates at a glance.
(cherry picked from commit 4e65210)
Co-authored-by: Pierre Jeambrun pierrejbrun@gmail.com