-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Print log when formatter ecosystem checks fail #6187
Conversation
PR Check ResultsBenchmarkLinux
Windows
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Extending the summary with some details would be helpful to ease reviewing.
It took me a bit of time to understand what I'm reviewing
- How did you test the change?
- we need it to unblock my reviews. What is it and what reviews?
I expected this to fail because it fails for me locally and now i'm confused. See #6188 for a proper failure |
**Summary** This includes two changes: * Allow settings `-v` in `ruff_dev`, using the `ruff_cli` code * `debug!` which configuration strategy was used This is a byproduct of debugging #6187. **Test Plan** n/a
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
This failed for me locally because i had Debugging this spawned #6193. |
Updated the summary |
this is cool. do you think we could get it to print the line containing the syntax error (ideally source + ruff output)? atm i still need to re-run locally to find the actual issue (unless i'm missing a trick here?) |
Unfortunately this is hard with our parser (it's not really meant for error recovery). I normally take the filename and let |
**Summary** This includes two changes: * Allow settings `-v` in `ruff_dev`, using the `ruff_cli` code * `debug!` which configuration strategy was used This is a byproduct of debugging #6187. **Test Plan** n/a
**Summary** This includes two changes: * Allow setting `-v` in `ruff_dev`, using the `ruff_cli` implementation * `debug!` which ruff configuration strategy was used This is a byproduct of debugging #6187. **Test Plan** n/a
Summary Print the errors when the formatter ecosystem checks failed. Im not happy that we current collect the log in the first place, but this is the less invasive change and we need it to unblock reviewing #6152.
Test Plan https://github.com/astral-sh/ruff/actions/runs/5713112075/job/15477879403?pr=6188