Live-share: [VS Code] Co-debugging isn't working

[carlosaicrag]

Describe what happened:
I work as an instructor at app academy coding Bootcamp and I've seen co-debugging work with just one student. One thing to note is that the student had recently gotten a new MacBook. other than that I see no difference between my computer and his computer. Another thing to note is that it works when he shares the live-share session with me but it doesn't work when I share a live-share session with him. I would really like for this to be fixed asap as it will serve as a great tool for the pair programming experience the students have with one another; especially during this time where we cannot be in person. Thank you in advance for looking into this and please reach out if you have any questions about what I've described.

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

Steps to Reproduce / Scenario:

1. launch a vs code live share session
2. invite a participant
3. write a simple javascript function and place a debugger within it
4. start a debugging session

what you'll notice is that the host will be able to debug but the invitee will not be able to.
the debugging console shows up but that's about it.

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.

[fubaduba]

Thank you for relaying your issue here. We will take a look at this, and get back to you.

[fubaduba]

@jramsay

[pjninnim]

My colleague and I are also seeing the same issue.

[linuscarlstrom]

We're experiencing the same issue at work, but our system configuration looks a little bit different. It worked perfectly fine a few weeks ago 👨‍💻

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

[pjninnim]

This issue has now been resolved for us in the latest update received today:

Version: 1.47.0-insider (user setup)
Commit: 8cd3fe080bee38d28ba01d0d71713d6ec22b254e
Date: 2020-06-19T06:35:49.048Z
Electron: 7.3.1
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Windows_NT x64 10.0.19041

[carlosaicrag]

I did the update, but my version is 1.46.1 not 1.47.0. The issue is still not resolved for me, unfortunately.

[WoodsCumming]

I have the same issue. I did the update 1.47.0-insider, but the issue is still not resolved.

[WoodsCumming]

版本: 1.47.0-insider
提交: 376d9d9d785ccca128fdbb16f001446d0ad64d32
日期: 2020-07-03T10:26:01.724Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.6.0

[carlosaicrag]

Hello, just wanted to see if there are any updates on this issue.

[MartinSalinas98]

I'm experiencing the same issue, both guest and host running Ubuntu 20.4, both with vscode 1.50.1.

[andig]

@maintainers: There are a number of similiar co-debug issues, for example another duplicate (for Go) with the exact same behaviour is https://github.com/MicrosoftDocs/live-share/issues/3970.

Is there anything we could do to move investigation/resolution further?

[andig]

Ping @fubaduba @jramsay any chance helping us to get co-debug back to working state on OSX?

[lostintangent]

@jramsay is looking into this right now, and we're prioritizing this issue 👍

[lostintangent]

Out of curiosity: what shell are folks using? We’re having a hard time narrowing down the issue here, and I’m just curious if the system shell could be a factor.

[pamarcos]

Out of curiosity: what shell are folks using? We’re having a hard time narrowing down the issue here, and I’m just curious if the system shell could be a factor.

I had the issue with Linux host and client and we both use zsh

[rbingham]

Out of curiosity: what shell are folks using? We’re having a hard time narrowing down the issue here, and I’m just curious if the system shell could be a factor.

I am on a mac using am using zsh.

[carlosaicrag]

Out of curiosity: what shell are folks using? We’re having a hard time narrowing down the issue here, and I’m just curious if the system shell could be a factor.

I am on a mac using bash

[andig]

Mac and zsh in hyperjs

[lostintangent]

This shouldn't be necessary, but could folks do me a huge favor and try installing .NET Core 3.1 (macOS, Windows, Linux) and seeing if that fixes co-debugging for them? We're still investigating, but it seems like we may have had a regression where the debugging support isn't using the Live Share-internal version of .NET Core, and therefore, it fails if you don't have it installed in the host machine. We're looking into this now, but it would be interesting to hear if this successfully unblocks anyone that is having this issue. Thanks!

[pamarcos]

This shouldn't be necessary, but could folks do me a huge favor and try installing .NET Core 3.1 (macOS, Windows, Linux) and seeing if that fixes co-debugging for them? We're still investigating, but it seems like we may have had a regression where the debugging support isn't using the Live Share-internal version of .NET Core, and therefore, it fails if you don't have it installed in the host machine. We're looking into this now, but it would be interesting to hear if this successfully unblocks anyone that is having this issue. Thanks!

Ubuntu 20.04 here. Before, remote debugging didn't work with this:

dotnet --version
2.2.402
dpkg -S $(which dotnet)
dotnet-host: /usr/bin/dotnet

Now it works as expected after running the following commands. So, there's that. Thanks for the suggestion :+1:

sudo apt remove dotnet-host && sudo apt install dotnet-sdk-3.1 dotnet-runtime-3.1
dotnet --version
3.1.404

Merry Xmas and Happy New Year! :partying_face:

[lostintangent]

@pamarcos Awesome! Thanks so much for confirming that workaround 🙌

We're pretty sure we identified the issue here, and we're working on getting the fix out ASAP. In particular, this issue should only impact Live Share hosts (not guests) running on macOS/Linux, and that don't have .NET 3.1 installed already. So in the meantime, if you install .NET 3.1, then you should be able to unblock yourself.

Thanks again for all the help and patience here, as we've tried to narrow this issue down. Stay tuned for another update soon!

[pjninnim]

I confirm that this workaround also works for us although both Guest and Host had to have this applied when Windows -> Windows with Ubuntu in WSL. Thanks!

[lostintangent]

Hey folks! To provide a quick update: we've made the fix for this issue, and it will be included in this week's release (~Wednesday). Thanks again for all the help with diagnosing this problem/workaround!

[lostintangent]

The fix for this has now been deployed to the marketplace. Thanks again for your patience and help in resolving this issue. Please let us know if you run into any issues, otherwise, I'll go ahead and close this as resolved 👍