-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReadError exception fails to mention the file generating the error. #261
Comments
ssbarnea
added a commit
to ssbarnea/yamllint
that referenced
this issue
May 2, 2020
Avoids confusing tracebacks when ReadErrors exceptions are raised from the yaml reader. Now we do print the filename that failed to load and stop processing in order to avoid additional exceptions. Also adds tests to prevent future regressions. Fixes: adrienverge#261
ssbarnea
added a commit
to ssbarnea/yamllint
that referenced
this issue
May 2, 2020
Avoids confusing tracebacks when ReadErrors exceptions are raised from the yaml reader. Now we do print the filename that failed to load and stop processing in order to avoid additional exceptions. Also adds tests to prevent future regressions. Fixes: adrienverge#261
ssbarnea
added a commit
to ssbarnea/yamllint
that referenced
this issue
May 2, 2020
Avoids confusing tracebacks when ReadErrors exceptions are raised from the yaml reader. Now we do print the filename that failed to load and stop processing in order to avoid additional exceptions. Also adds tests to prevent future regressions. Fixes: adrienverge#261
ssbarnea
added a commit
to ssbarnea/yamllint
that referenced
this issue
May 2, 2020
Avoids confusing tracebacks when ReadErrors exceptions are raised from the yaml reader. Now we do print the filename that failed to load and stop processing in order to avoid additional exceptions. Also adds tests to prevent future regressions. Fixes: adrienverge#261
ssbarnea
added a commit
to ssbarnea/yamllint
that referenced
this issue
May 3, 2020
Avoids confusing tracebacks when ReadErrors exceptions are raised from the yaml reader. Now we do print the filename that failed to load and stop processing in order to avoid additional exceptions. Also adds tests to prevent future regressions. Fixes: adrienverge#261
ssbarnea
added a commit
to ssbarnea/yamllint
that referenced
this issue
Oct 9, 2020
Avoids confusing tracebacks when ReadErrors exceptions are raised from the yaml reader. Now we do print the filename that failed to load and stop processing in order to avoid additional exceptions. Also adds tests to prevent future regressions. Fixes: adrienverge#261
ssbarnea
added a commit
to ssbarnea/yamllint
that referenced
this issue
Mar 16, 2023
Avoids confusing tracebacks when ReadErrors exceptions are raised from the yaml reader. Now we do print the filename that failed to load and stop processing in order to avoid additional exceptions. Also adds tests to prevent future regressions. Fixes: adrienverge#261
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While the error causing the exception seems to be caused by #218 what makes it much worse is the it produces an output which makes impossible to identify the filename causing the problem:
At minimum, the filename must be mentioned.
The text was updated successfully, but these errors were encountered: