Connected Live Share sessions occasionally modify local code during remote shared development

[Alan3344]

Describe what happened:
When I used vsc to connect to Live Share to remotely write Golang test code, I clicked *testing.T to view its references. As soon as a part of the content was selected, it was deleted. I had to press Ctrl+Z repeatedly to undo the operation, but it didn't help. Later I realized that by quickly clicking on the editor interface and unselecting this part of the code, it was restored.

It is impossible to describe it in detail, please check the demonstration video below

From time to time, several code files and code snippets were generated for me.

What was your system configuration?
Product and Version [VS/VSCode]:
OS Version[macOS/Windows]:
Live Share Extension Version:
Target Platform or Language [e.g. Node.js]:

Version: 1.96.0 (user setup)
Commit: 138f619c86f1199955d53b4166bef66ef252935c
Date: 2024-12-11T02:29:09.626Z
Electron: 32.2.6
ElectronBuildId: 10629634
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Windows_NT x64 10.0.26100

Installation
Identifier
ms-vsliveshare.vsliveshare
Version
1.0.5941
Last updated
2024-09-24, 14:17:06
Size
25.1 MB
Market
Released
2018-01-30, 02:04:53
Last published
2024-09-24, 04:43:52

Steps to Reproduce / Scenario:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Please attach logs to this issue:
You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue

Screenshots
If applicable, add screenshots to help explain your problem.

No logs

It should also be generated when I selected the code segment (just when I wanted to delete it)

bandicam-2024-12-15_02-00-45-313_2.mp4

[thiagokisaki]

I am experiencing the same issue while using Live Share to collaborate on a Go codebase.

[samuelchristlie]

I'm experiencing the same issue

[lalaithion]

I have experienced a similar issue, and replicated it in a clean VSCode install with no configuration aside from Live Share and the Go language extension. People who join the shared session (also with clean VSCode installs with just Live Share added) and command-click (macOS) on a reference cause the referenced function to be extracted out of its current file into a new file, and have a second file created with unit tests auto-generated for that function. This does not occur for the host, and may be an unintended reaction between the Live Share extension and the Go language extension.

[lisaSW]

I have experienced a similar issue, and replicated it in a clean VSCode install with no configuration aside from Live Share and the Go language extension. People who join the shared session (also with clean VSCode installs with just Live Share added) and command-click (macOS) on a reference cause the referenced function to be extracted out of its current file into a new file, and have a second file created with unit tests auto-generated for that function. This does not occur for the host, and may be an unintended reaction between the Live Share extension and the Go language extension.

My teammate and I are experiencing this same exact thing.

[seralogar]

Exactly same issue here, also on Mac.

[SKPG-Tech]

These issues seem to be connected. #5155

[RanPix]

Downgrading the gopls version (0.16.2) seems to help with this issue. (Make sure you have go tools auto update disabled in go extension settings)

[seralogar]

Master version of gopls solves it. All participants of the live share session need to update, otherwise it will still fail.