Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixes for VSCode attached debugging and related improvements. #777

Closed
wants to merge 1 commit into from

Conversation

ecosky
Copy link
Contributor

@ecosky ecosky commented Jan 19, 2025

'launch' and 'attach' modes are working with these changes. The root problems were related to the version of the attached project not being detected properly and file paths not being correctly calculated when attached. The networking code that had version-dependent behavior is now a bit more robust and won't break if minor versions were to ever exceed 1 digit. When using 'attach' mode, the version info wasn't available at all, causing most (all?) network messages to be ignored.

Tested with attach and launch modes, and with a built vsix.

'launch' and 'attach' modes are working with these changes. The root problems were related to the version of the attached project not being detected properly and file paths not being correctly calculated when attached. The networking code that had version-dependent behavior is now a bit more robust and won't break if minor versions were to ever exceed 1 digit.
When using 'attach' mode, the version info wasn't available at all, causing most (all?) network messages to be ignored.
@DaelonSuzuka
Copy link
Collaborator

Hey @ecosky, thanks for contributing this, and I'm really excited to see attach sessions finally working, but unfortunately I'm going to have to ask you to resubmit this PR with your changes in a branch named something other than master.

Having your changes in the master branch makes it harder for reviewers because checking out your branch will conflict with my local master branch.

@ecosky
Copy link
Contributor Author

ecosky commented Jan 26, 2025

Hi there, that makes sense. I'll put it in a different branch and submit a different PR.

@DaelonSuzuka
Copy link
Collaborator

Thanks for understanding!

@ecosky
Copy link
Contributor Author

ecosky commented Jan 26, 2025

Sure thing! Here you go: #784

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants