-
Notifications
You must be signed in to change notification settings - Fork 53
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
Improve logging in VSCode extension #526
Comments
Hi, thanks for opening this issue. Can you provide the following information:
I think some of this has been fixed and some has been released. Can you check if you're on the latest version of the VS Code extension ( |
There are couple of PRs which have improved the logging on Regarding the warnings that you're seeing in the following screenshot:
This should be fixed in the latest Ruff version via astral-sh/ruff#12252. We're going to be releasing a new version of the VS Code extension soon. I'd appreciate if you can try it with the latest version then and check if you're facing the same problems. |
I've just updated VSCode and this is looking pretty good now! Thanks for your work and much appreciated, this will make debugging issues a lot easier. It does still show the pandas noise, but this is not a huge issue. |
That's fixed in astral-sh/ruff#11590, you might want to upgrade the |
Hi,
Today I noticed that the version of Ruff that's used by the LSP and the version that we have installed in our .venvs do not seem to be in sync:
In order to debug this, I went to the Output -> Ruff screen and that shows following information:
It would be useful to add the following information:
In addition to the above, it seems that every time I press save it prints the following log lines:
The text was updated successfully, but these errors were encountered: