Improve the error message displayed when there is a webserver error #36570
Conversation
This file contains 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
The error message displayed when errors happen in the webserver did not properly communicated, that the user MUST look at the logs and provide more information to investigate the root cause (after looking at the logs themselves). We have a number of users just copy&pasting the generic error message without understanding that this is not nearly enough to help them. This PR proposes a bit more explicit call to look at the logs and explains why details are not displayed (for security reasons).
potiuk
requested review from
ryanahamilton,
ashb,
bbovenzi and
pierrejeambrun
as code owners
boring-cyborg
bot
added
area:UI
syedahsn
approved these changes
Jan 3, 2024
hussein-awala
approved these changes
Jan 3, 2024
ephraimbuddy
pushed a commit
that referenced
this pull request
Jan 11, 2024
…36570) The error message displayed when errors happen in the webserver did not properly communicated, that the user MUST look at the logs and provide more information to investigate the root cause (after looking at the logs themselves). We have a number of users just copy&pasting the generic error message without understanding that this is not nearly enough to help them. This PR proposes a bit more explicit call to look at the logs and explains why details are not displayed (for security reasons). (cherry picked from commit 574f86e)
abhishekbhakat
pushed a commit
to abhishekbhakat/my_airflow
that referenced
this pull request
Mar 5, 2024
…pache#36570) The error message displayed when errors happen in the webserver did not properly communicated, that the user MUST look at the logs and provide more information to investigate the root cause (after looking at the logs themselves). We have a number of users just copy&pasting the generic error message without understanding that this is not nearly enough to help them. This PR proposes a bit more explicit call to look at the logs and explains why details are not displayed (for security reasons).
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.
The error message displayed when errors happen in the webserver did not properly communicate, that the user MUST look at the logs and provide more information to investigate the root cause (after looking at the logs themselves). We have a number of users just copy&pasting the generic error message without understanding that this is not nearly enough to help them.
This PR proposes a bit more explicit call to look at the logs and explains why details are not displayed (for security reasons).
^ 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.