Track debugging sessions until csdevkit is initialized #6480
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
WardenGnaw
approved these changes
Oct 3, 2023
gregg-miskelly
approved these changes
Oct 11, 2023
dibarbet
approved these changes
Oct 11, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
When using C# dev kit with C# extension, there was a bug that hot reload might not initialize on the first debugging session. This happened due to a race condition that the 'launch' command is fired before the C# dev kit finishes initializing, so no
brokeredServicePipeNameis passed to the debugger.Fix
Starts tracking the debugging session until C# dev kit is initialized. If there is an existing debugging session, this sends a custom
initializeBrokeredServicePipeNamerequest with the pipe name.