Skip to content

node debugging seems not to be working. ever attaches #312

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

Closed
polymerchm opened this issue Mar 21, 2019 · 13 comments
Closed

node debugging seems not to be working. ever attaches #312

polymerchm opened this issue Mar 21, 2019 · 13 comments
Assignees
Milestone

Comments

@polymerchm
Copy link

No description provided.

@polymerchm
Copy link
Author

When running in the shell, with either auto accath or with an attach "task", never seems to connect.

@NGTmeaty
Copy link
Contributor

Can you please fill out the template so we can have more information?

@nol166
Copy link
Contributor

nol166 commented Mar 21, 2019

Hey, @polymerchm can you send us the output of the error message you are getting or the error in the browser developer console?

@nol166 nol166 added the waiting-for-info Waiting for more information from submitter label Mar 21, 2019
@polymerchm
Copy link
Author

This is the output in the "output" window with "trace" enabled in the attach options:

Error: Cannot find module 'vscode-chrome-debug-core'
at Module.r.require (/usr/local/bin/code-server:468:26539)
at /home/travis/build/codercom/code-server/packages/server/build/extensions/ms-vscode.node-debug2/out/src/nodeDebug.js/home/travis/build/codercom/code-server/packages/server/build/extensions/ms-vscode.node-debug2/out/src/nodeDebug.js:6:36
at requireFilesystemModule (/usr/local/bin/code-server:468:26288)
at Object.exports.requireFork (/usr/local/bin/code-server:468:26641)
at v.run (/usr/local/bin/code-server:549:49569)
at

@nol166
Copy link
Contributor

nol166 commented Mar 21, 2019

Hey @polymerchm node debugging should be fixed in an upcoming update very soon.

@nol166
Copy link
Contributor

nol166 commented Mar 21, 2019

This will probably be fixed by #299

@jondavidschober
Copy link

jondavidschober commented Mar 22, 2019

I'm having the same issue. I dont have any extensions installed except themes. The output is

 [2019-03-22 18:42:28.087] [exthost] [info] eager extensions activated
 [2019-03-22 18:42:57.484] [exthost] [info] ExtensionService#_doActivateExtension vscode.debug-server-ready {"startup":false,"activationEvent":"onDebugResolve"}
 [2019-03-22 18:42:57.485] [exthost] [info] ExtensionService#loadCommonJSModule /home/travis/build/codercom/code-server/packages/server/build/extensions/debug-server-ready/dist/extension
 [2019-03-22 18:42:57.488] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode.node-debug2 {"startup":false,"activationEvent":"onDebugResolve:node"}
 [2019-03-22 18:42:57.488] [exthost] [info] ExtensionService#loadCommonJSModule /home/travis/build/codercom/code-server/packages/server/build/extensions/ms-vscode.node-debug2/out/src/extension
 [2019-03-22 18:42:57.524] [exthost] [info] ExtensionService#_doActivateExtension ms-vscode.node-debug {"startup":false,"activationEvent":"onDebugResolve:node"}
 [2019-03-22 18:42:57.524] [exthost] [info] ExtensionService#loadCommonJSModule /home/travis/build/codercom/code-server/packages/server/build/extensions/ms-vscode.node-debug/dist/extension.js`

I'm trying to attach to existing node with inspector running. The node process never prints Debugger attached.

I basically get one shot of starting the debugger, it kinda hangs then goes away, then if I try debugging again I get "There is already a debug configuration "Attach" running."

@NGTmeaty
Copy link
Contributor

What version of code-server are you running?

@polymerchm
Copy link
Author

polymerchm commented Mar 23, 2019 via email

@foresthoffman
Copy link
Contributor

@polymerchm The blank screen after attempting to add a folder will be fixed by #317 in the next release.

@jondavidschober
Copy link

@NGTmeaty 1.32.0-310

@kylecarbs kylecarbs self-assigned this Mar 26, 2019
@kylecarbs kylecarbs removed the waiting-for-info Waiting for more information from submitter label Mar 26, 2019
@kylecarbs kylecarbs added this to the March 2019 milestone Mar 26, 2019
@kylecarbs
Copy link
Member

Fixed with the latest release.

@NGTmeaty
Copy link
Contributor

Thanks Kyle!

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

No branches or pull requests

6 participants