Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

fix: Fix debug debugger tasks and guide #2013

Merged
merged 2 commits into from
Oct 20, 2018

Conversation

alexdor
Copy link
Contributor

@alexdor alexdor commented Oct 16, 2018

I was trying to tackle #1529 and while trying to follow the guide from https://github.com/Microsoft/vscode-go/tree/master/src/debugAdapter I faced a few errors and saw an old task that had deprecated options. This pr fixes those issues and updates the task's option according to the recent spec.

@msftclas
Copy link

msftclas commented Oct 16, 2018

CLA assistant check
All CLA requirements met.

@alexdor
Copy link
Contributor Author

alexdor commented Oct 16, 2018

@ramya-rao-a all the test that have failed here have been fixed at #2014 I can push the commits here as well if you want or I can wait until #2014 is merged and rebase this one on top of it, which one do you prefer?

@@ -13,6 +13,6 @@ cd vscode-go
npm install
```
2. Open the `vscode-go` folder in one instance. Choose the `Launch Extension` debug target and hit F5 to launch a second instance.
3. In the second instance, open the Go application you'd like to test against. In that instance, create a new Go debug target pointing at the program you want to debug, and add `"debugServer": 4711` in the root of the configuration.
3. In the second instance, open the Go application you'd like to test against. In that instance, create a new Go debug target pointing at the program you want to debug, and add `"debugServer": 4712` in the root of the configuration.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why 4712?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

@ramya-rao-a ramya-rao-a left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@alexdor The tests are fixed in the master branch. Can you rebase/merge from master?

@alexdor
Copy link
Contributor Author

alexdor commented Oct 16, 2018

@ramya-rao-a I've rebased my commit

"args": [
"--extensionDevelopmentPath=${workspaceFolder}"
],
"args": ["--extensionDevelopmentPath=${workspaceRoot}"],
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was another PR that got merged to master which replaced all $workspaceRoot instances with $workspaceFolder.

I believe the net change you want here is to change the version number. Can you undo the other changes in this file?

@alexdor
Copy link
Contributor Author

alexdor commented Oct 20, 2018

@ramya-rao-a I've done the changes that you requested above and fixed the deprecation warning from this 7afe072#diff-3090e25fed17a6bd57433c6bbadc451aL22

@ramya-rao-a ramya-rao-a merged commit 4038739 into microsoft:master Oct 20, 2018
@ramya-rao-a ramya-rao-a mentioned this pull request Oct 20, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants