You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This really need to be solved upstream. Essentially, one of the tools applies first, VS Code should synchronize the changes to all servers. This does not happen when using an import sorter. So the second tool sees the wrong version of the document.
Sam Duke (@samskiter) a workaround and a faster tool here is Ruff (ruff extension is available in the market place). It supports isort style import sorting and black style of formatting, and several linters in a single tool.
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Sam Duke (@samskiter) as I mentioned in my comment. This can’t be fixed in extension the issue is microsoft/vscode#174295 . I created that issue when I noticed the problem when I created this extension. I don’t see any change we can do locally to address this. It should be addressed in VS Code.
Activity
eleanorjboyd commentedon Oct 28, 2025
Karthik Nadig (@karthiknadig) the tagged issue was filed by you originally - any ideas that could help here?
karthiknadig commentedon Oct 28, 2025
This really need to be solved upstream. Essentially, one of the tools applies first, VS Code should synchronize the changes to all servers. This does not happen when using an import sorter. So the second tool sees the wrong version of the document.
karthiknadig commentedon Oct 28, 2025
Sam Duke (@samskiter) a workaround and a faster tool here is Ruff (ruff extension is available in the market place). It supports isort style import sorting and black style of formatting, and several linters in a single tool.
neilferreira commentedon Oct 30, 2025
I'm seeing this with black and isort. Any workarounds available?
karthiknadig commentedon Oct 30, 2025
Neil Ferreira (@neilferreira) see #25538 (comment) for workaround
github-actions commentedon Nov 29, 2025
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Happy Coding!
samskiter commentedon Nov 29, 2025
What there was no info requested, pls reopen!
samskiter commentedon Nov 29, 2025
Reopen
samskiter commentedon Nov 29, 2025
Reopen
karthiknadig commentedon Nov 30, 2025
Sam Duke (@samskiter) as I mentioned in my comment. This can’t be fixed in extension the issue is microsoft/vscode#174295 . I created that issue when I noticed the problem when I created this extension. I don’t see any change we can do locally to address this. It should be addressed in VS Code.