Describe the bug
When the plugin calls ruff binary and it exits with an unexpected error (e.g. there is a typo in ruff.toml), the user will not get notified about that, but instead, an IDE exception is being raised. Since those are not easy to find (small red icon in the right corner) and require you to parse Kotlin traceback message with your eyes it is difficult to debug the exact cause of an error.
To Reproduce
Steps to reproduce the behavior:
- Create sample
ruff.tomlwith the following contents:
python = "3.12" - In the plugin settings choose this file as a chosen Ruff configuration.
- Make some changes to an open Python file.
- Save the file.
Expected behavior
A pop-up that relays the exact error message produced by failed ruff run.
Environments (please complete the following information):
- IDE: PY-232.10072.31
- OS: macOS Ventura 13.6
- Ruff Version: 0.0.292
- Plugin version: 0.0.24
If you agree that this is a valid issue but don't have time to work on it, I can make a PR for that.
How does funding with Polar work?
Pay now to fund the work behind this issue.
Get updates on progress being made.
Maintainer is rewarded once the issue is completed.
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too