Uh oh!
There was an error while loading. Please reload this page.
openlineage: provide stack trace under proper key in error facet - #40372
Merged
Conversation
Signed-off-by: Kacper Muda <mudakacper@gmail.com>
mobuchowski
approved these changes
Jun 21, 2024
kacpermuda
commented
Jun 24, 2024
CollaboratorAuthor
It's ready to merge, whenever some committer has time ^^ |
potiuk
approved these changes
Jun 24, 2024
20 tasks
romsharon98 pushed a commit
to romsharon98/airflow
that referenced
this pull request
Jul 26, 2024
Signed-off-by: Kacper Muda <mudakacper@gmail.com>
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
I misplaced the stacktrace when implementing it in #39813, it should be available under
stackTraceand notmessage.^ 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 newsfragments.