Source actions not appearing in VS Code integration

[snowsignal]

Overview

VS Code shows no source actions available when running Command Palette > Source Action... in a file with several auto-fixable problems and disorganized imports. Both of the supported source actions, source.fixAll and source.organizeImports, should show up.

I suspect an issue in our server implementation, hence why I'm filing this as a ruff-lsp issue.

Details

• Ruff version: v0.3.3
• ruff-lsp version: v0.0.53
• ruff-vscode version: 2024.16.0
• Tested on the scipy codebase, commit 488db3d39dae9f65d61d6dc1f4bccdcea92321cd, file scipy/special/tests/test_basic.py. A tool.ruff section was added to the pyproject.toml, with select = ["ALL"] as the only provided configuration.

[charliermarsh]

Interesting. Should those actions definitely be visible there? The official isort extension from Microsoft doesn't seem to show them either. In my experience users typically run these by name:

[snowsignal]

@charliermarsh Those actions should definitely be visible. It's true that we also support command execution as a way to perform the same actions, which is probably what most users do, but I'm worried that this also affects editors that show source actions more visibly, like Neovim (though I still need to see if this can be reproduced there).

[smsossah]

I'm running into the same issue with neovim and it was working previously. I'm getting a "No code actions available" and I was able to narrow it down to ruff-lsp as well @snowsignal @charliermarsh. (Edited) Everything works as expected when I downgrade to 0.0.52. Seems to be a bug with 0.0.53

[dhruvmanila]

@smsossah Can you open a new issue with all the relevant details? These could be your Neovim setup, Ruff version, etc.