Display API Sever errors in task logs & fail task on error#48580
Merged
kaxil merged 1 commit intoapache:mainfrom Mar 31, 2025
Merged
Display API Sever errors in task logs & fail task on error#48580kaxil merged 1 commit intoapache:mainfrom
kaxil merged 1 commit intoapache:mainfrom
Conversation
Follow-up of apache#48517 Currently, when a task fails due to API Server error, the task logs shows nothing, and the task continues running. It also leads to the pickling issue on LocalExecutor that was fixed by apache#48517. This PR improves upon it and propogates the API server error in the task UI and fails the task.
jedcunningham
approved these changes
Mar 31, 2025
shubham-pyc
pushed a commit
to shubham-pyc/airflow
that referenced
this pull request
Apr 2, 2025
) Follow-up of apache#48517 Currently, when a task fails due to API Server error, the task logs shows nothing, and the task continues running. It also leads to the pickling issue on LocalExecutor that was fixed by apache#48517. This PR improves upon it and propogates the API server error in the task UI and fails the task.
nailo2c
pushed a commit
to nailo2c/airflow
that referenced
this pull request
Apr 4, 2025
) Follow-up of apache#48517 Currently, when a task fails due to API Server error, the task logs shows nothing, and the task continues running. It also leads to the pickling issue on LocalExecutor that was fixed by apache#48517. This PR improves upon it and propogates the API server error in the task UI and fails the task.
diogotrodrigues
pushed a commit
to diogotrodrigues/airflow
that referenced
this pull request
Apr 6, 2025
) Follow-up of apache#48517 Currently, when a task fails due to API Server error, the task logs shows nothing, and the task continues running. It also leads to the pickling issue on LocalExecutor that was fixed by apache#48517. This PR improves upon it and propogates the API server error in the task UI and fails the task.
simonprydden
pushed a commit
to simonprydden/airflow
that referenced
this pull request
Apr 8, 2025
) Follow-up of apache#48517 Currently, when a task fails due to API Server error, the task logs shows nothing, and the task continues running. It also leads to the pickling issue on LocalExecutor that was fixed by apache#48517. This PR improves upon it and propogates the API server error in the task UI and fails the task.
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.
Follow-up of #48517
Currently, when a task fails due to API Server error, the task logs shows nothing, and the task continues running.
It also leads to the pickling issue on LocalExecutor that was fixed by #48517.
This PR improves upon it and propogates the API server error in the task UI and fails the task.
^ 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 airflow-core/newsfragments.