Pavel Minaev
Pavel Minaev
The reason why this happens is because we call the formatters with a switch to produce a .diff patch, which we then apply to the document (IIRC this is so...
I don't think we can do the second option. The whole reason why this line occurs in the diff is because Black etc are trying to add a newline there,...
The issue here is broader than breakpoints; the debug session is simply never set up properly, so nothing is actually being debugged. The problem is that the test executor process...
The reason why it's not propagated is due to timing of processes involved. In VS 2022, there's a grand total of 4 processes here end-to-end, spawned like so: VS →...
Looking at NTVS (which was originally a fork), they worked around this by using WMI to look up the "devenv" parent process. This is a viable *short-term* fix, but we...
This document covers the preferred approach: https://github.com/microsoft/vstest-docs/blob/main/RFCs/0029-Debugging-External-Test-Processes.md It seems that the changes necessary to do things "the right way" might not be that extensive, after all.
When python.exe from the Store is spawned to run the tests, it exits with `STATUS_DLL_NOT_FOUND` (0xC0000135). Process Monitor records the following failures:  The relevant ones are the last three,...
The owners of covrun64.dll - but that should be owned by whoever owns code coverage in VS. It's not a Windows component - it tries to look it up in...
The dropdown for `import` completions doesn't show up in general, not even for standard modules. However, once the import is typed, using the module works, and completions appear for its...
Likely caused by LSP protocol incompatibilities. It works in 17.3.0 Preview 3.0 [32607.526.main], where the LSP client is updated. Can you please re-check on that version?