v2021.2.576481509 breaks LiveSharing
See original GitHub issueEnvironment data
- VS Code version: 1.53.2
- Extension version (available under the Extensions sidebar): v2021.2.576481509
- OS and version: Windows_NT x64 10.0.19042
- Python version (& distribution if applicable, e.g. Anaconda): 3.9.0
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): XXX
- Relevant/affected Python packages and their versions: XXX
- Relevant/affected Python-related VS Code extensions and their versions: Pylance (v2021.2.3), Live Share (v1.0.3784)
- Value of the
python.languageServer
setting: pylance
[NOTE: If you suspect that your issue is related to the Microsoft Python Language Server (python.languageServer: 'Microsoft'
), please download our new language server Pylance from the VS Code marketplace to see if that fixes your issue]
Expected behaviour
I can join a LiveShare session and then open a python file.
Actual behaviour
The “Guest” can join a LiveShare Session and have access to “Host” files and terminal but if the “Guest” opens a python file then the “Guest” machine will free after “Loading Python Extension” pops up in the lower tool bar.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
-
Have a Amazon Workspaces Host machine with VSCode 1.53.2 and Microsoft Python v2021.2.576481509 and pylance latest version.
-
Have a Windows 10 + WSL backend Guest machine with VSCode 1.53.2 and Microsoft Python v2021.2.576481509 and pylance latest version.
-
Invite Windows 10 Guest from the Linux host.
-
Open python file from the Guest machine.
-
LiveShare “freezes” for the Guest.
Logs
Output for Python
in the Output
panel (View
→Output
, change the drop-down the upper-right of the Output
panel to Python
)
Guest Python
User belongs to experiment group 'pythonaa'
User belongs to experiment group 'pythonSendEntireLineToREPL'
User belongs to experiment group 'pythonInstallPylintButtonFirstcf'
User belongs to experiment group 'ShowPlayIcon - start'
User belongs to experiment group 'DebugAdapterFactory - experiment'
User belongs to experiment group 'PtvsdWheels37 - experiment'
User belongs to experiment group 'UseTerminalToGetActivatedEnvVars - control'
User belongs to experiment group 'AA_testing - control'
User belongs to experiment group 'LocalZMQKernel - experiment'
User belongs to experiment group 'CollectLSRequestTiming - control'
User belongs to experiment group 'CollectNodeLSRequestTiming - experiment'
User belongs to experiment group 'EnableIPyWidgets - experiment'
User belongs to experiment group 'RunByLine - experiment'
User belongs to experiment group 'CustomEditorSupport - control'
Guest Log (Window)
[2021-02-18 03:52:52.123] [renderer1] [error] ENOENT: no such file or directory, unlink '/home/shadycuz/.local/share/vsliveshare/cascade.json': Error: ENOENT: no such file or directory, unlink '/home/shadycuz/.local/share/vsliveshare/cascade.json'
[2021-02-18 03:52:52.400] [renderer1] [error] spawn \tmp\vsliveshare\tmp-7A1017D6975480214F4CBEB2496E6CF65E98\git ENOENT: Error: spawn \tmp\vsliveshare\tmp-7A1017D6975480214F4CBEB2496E6CF65E98\git ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
at onErrorNT (internal/child_process.js:469:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
[2021-02-18 04:10:07.127] [renderer1] [error] ENOENT: no such file or directory, unlink '/home/shadycuz/.local/share/vsliveshare/cascade.json': Error: ENOENT: no such file or directory, unlink '/home/shadycuz/.local/share/vsliveshare/cascade.json'
[2021-02-18 04:10:07.396] [renderer1] [error] spawn \tmp\vsliveshare\tmp-D8E9800B0338D6B93C615580E99F8E468049\git ENOENT: Error: spawn \tmp\vsliveshare\tmp-D8E9800B0338D6B93C615580E99F8E468049\git ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
at onErrorNT (internal/child_process.js:469:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
[2021-02-18 04:12:00.651] [renderer1] [error] ENOENT: no such file or directory, unlink '/home/shadycuz/.local/share/vsliveshare/cascade.json': Error: ENOENT: no such file or directory, unlink '/home/shadycuz/.local/share/vsliveshare/cascade.json'
[2021-02-18 04:12:00.651] [renderer1] [error] spawn \tmp\vsliveshare\tmp-D8E9800B0338D6B93C615580E99F8E468049\git ENOENT: Error: spawn \tmp\vsliveshare\tmp-D8E9800B0338D6B93C615580E99F8E468049\git ENOENT
at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
at onErrorNT (internal/child_process.js:469:16)
at processTicksAndRejections (internal/process/task_queues.js:84:21)
[2021-02-18 04:12:00.651] [renderer1] [warning] Workbench did not finish loading in 10 seconds, that might be a problem that should be reported.
[2021-02-18 04:12:22.481] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
[2021-02-18 04:12:22.481] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] resolving connection...
[2021-02-18 04:12:22.481] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] connecting to 172.29.129.234:32863...
[2021-02-18 04:12:22.538] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] reconnected!
[2021-02-18 04:12:43.176] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
[2021-02-18 04:12:43.177] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] resolving connection...
[2021-02-18 04:12:43.177] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] connecting to 172.29.129.234:32863...
[2021-02-18 04:12:43.245] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] reconnected!
[2021-02-18 04:13:04.179] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
[2021-02-18 04:13:04.180] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] resolving connection...
[2021-02-18 04:13:04.180] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] connecting to 172.29.129.234:32863...
[2021-02-18 04:13:04.248] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] reconnected!
[2021-02-18 04:13:24.252] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
[2021-02-18 04:13:24.252] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] resolving connection...
[2021-02-18 04:13:24.252] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] connecting to 172.29.129.234:32863...
[2021-02-18 04:13:24.310] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] reconnected!
[2021-02-18 04:13:44.316] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
[2021-02-18 04:13:44.317] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] resolving connection...
[2021-02-18 04:13:44.317] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] connecting to 172.29.129.234:32863...
[2021-02-18 04:13:44.380] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] reconnected!
[2021-02-18 04:14:04.385] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
[2021-02-18 04:14:04.386] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] resolving connection...
[2021-02-18 04:14:04.386] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] connecting to 172.29.129.234:32863...
[2021-02-18 04:14:04.445] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] reconnected!
[2021-02-18 04:14:24.461] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
[2021-02-18 04:14:24.462] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] resolving connection...
[2021-02-18 04:14:24.462] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] connecting to 172.29.129.234:32863...
[2021-02-18 04:14:24.519] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] reconnected!
[2021-02-18 04:14:44.523] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] starting reconnecting loop. You can get more information with the trace log level.
[2021-02-18 04:14:44.523] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] resolving connection...
[2021-02-18 04:14:44.523] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] connecting to 172.29.129.234:32863...
[2021-02-18 04:14:44.596] [renderer1] [info] [remote-connection][ExtensionHost][4ae05…][reconnect] reconnected!
...
I did some experimenting and live share only crashes when the Guest has the latest python extension version. Rolling back the guests python extension to v2021.2.576481509
fixes the liveshare issue.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (1 by maintainers)
Top GitHub Comments
Hi @luigiMinardi, please open a separate issue since things have changed since then. Thank you!
I’m going to close as it appears to be fixed now ❤️