Live-share: Joined user unable to see debugging stopped when Pause is pressed

[TylerLeonhardt]

Product and Version: VSCode
OS Version: macOS (host) Windows (joined)
Live Share Extension Version: 0.3.1071
Target Platform or Language [e.g. Node.js]: C#
VSCode version: Tested on 1.30 and 1.31 (insiders)

Steps to Reproduce / Scenario:

1. Start debugging - using C#'s attach to process launch task
2. Hit Pause debugger ( the pause button)

The joined user does not see that debugging has stopped - however the host shows that it has stopped on some code.

I thought this might have been related to https://github.com/MicrosoftDocs/live-share/issues/1266 because a lot of my files were "missing" to the joined user but I deleted my gitignore and the issue still occurred.

@SeeminglyScience can you attach the logs from our session?

For context, we were trying to debug PowerShell Editor Services which is the language server for the PowerShell extension for vscode

[SeeminglyScience]

Here are the logs for our session:

Host (macOS)

Client (Windows)

[lostintangent]

Thanks for the report and logs! We’ll look into this ASAP. Do you recall whether the guest’s debugger would stop if you hit a breakpoint? I’m just curious if there’s something specific to the pause action, or guest debugging in general.

[TylerLeonhardt]

Unfortunately we never tried that. I'll see if we can find some time to give it a go - don't block on us though!

[lostintangent]

We definitely won’t! I was just curious if you happened to notice. Thanks again for reporting this.

[SeeminglyScience]

@lostintangent We were able to try it with a breakpoint and that worked without issue. Looks like it's the pause action specifically. Here's the logs from our second session where we had a successful stopped event via breakpoint then a failed manual pause after continuing.

Host (macOS)

Client (Windows)

[lostintangent]

Thanks for confirming that! Sounds like we had a regression with debug pausing, and we’ll try to get a fix out ASAP.

[TylerLeonhardt]

Has there been any work done here? Wondering if I should grab a partner and try again.

[lostintangent]

This was caused by a regression in VS Code. The fix for that should be in the latest stable release, so it would great if you confirm whether you’re still experiencing it or not 👍

[lostintangent]

As a total aside, you can join your own Live Share sessions from another VS Code instance, if you’re ever simply looking to try to repro an issue or validate a fix. I just tried this issue and it no longer repros for me. But I’d love to get your confirmation that it’s resolved.

[TylerLeonhardt]

Sounds good! @SeeminglyScience and I might be spinning up a session tomorrow to try again from the original issue so I'll let you know how it goes!

[lostintangent]

This should have been resolved. Please let us k ow if that isn’t the case!