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

Activity

1. polymerchm commented on Mar 21, 2019

   

   polymerchm

   on Mar 21, 2019

   Author

   More actions

   When running in the shell, with either auto accath or with an attach "task", never seems to connect.
2. NGTmeaty commented on Mar 21, 2019

   

   NGTmeaty

   on Mar 21, 2019

   Contributor

   More actions

   Can you please fill out the template so we can have more information?
3. nol166 commented on Mar 21, 2019

   

   nol166

   on Mar 21, 2019

   Contributor

   More actions

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

   added

   waiting-for-infoWaiting for more information from submitterWaiting for more information from submitter

   on Mar 21, 2019
5. polymerchm commented on Mar 21, 2019

   

   polymerchm

   on Mar 21, 2019

   Author

   More actions

   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
6. nol166 commented on Mar 21, 2019

   

   nol166

   on Mar 21, 2019

   Contributor

   More actions

   Hey @polymerchm node debugging should be fixed in an upcoming update very soon.
7. nol166 commented on Mar 21, 2019

   

   nol166

   on Mar 21, 2019

   Contributor

   More actions

   This will probably be fixed by #299
8. jondavidschober commented on Mar 22, 2019

   

   jondavidschober

   on Mar 22, 2019

   Last edited by jondavidschober

   More actions

   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."
9. NGTmeaty commented on Mar 23, 2019

   

   NGTmeaty

   on Mar 23, 2019

   Contributor

   More actions

   What version of code-server are you running?
10. polymerchm commented on Mar 23, 2019

    

    polymerchm

    on Mar 23, 2019 via email

    Author

    More actions

    -310.Worked when I removed the chrome debugger module.Then tried to add a folder.Now just get black screen after the password screen. Sent from Xfinity Connect App

    …

    ------ Original Message ------ From: NGTmeaty To: codercom/code-server Cc:StevenPollack, Mention Sent: March 22, 2019 at 5:10 PM Subject: Re: [codercom/code-server] node debugging seems not to be working. ever attaches (#312) What version of code-server are you running? — You are receiving this because you were mentioned. Reply to this email directly,view it on GitHub(#312 (comment)), ormute the thread(https://github.com/notifications/unsubscribe-auth/AGHfku-kmuEiTgghm12jycly3ZNvOc6Mks5vZXD7gaJpZM4cB8zX).
11. foresthoffman commented on Mar 23, 2019

    

    foresthoffman

    on Mar 23, 2019

    Contributor

    More actions

    @polymerchm The blank screen after attempting to add a folder will be fixed by #317 in the next release.
12. jondavidschober commented on Mar 23, 2019

    

    jondavidschober

    on Mar 23, 2019

    More actions

    @NGTmeaty 1.32.0-310
13. kylecarbs

    self-assigned this

    on Mar 26, 2019
14. kylecarbs

    removed

    waiting-for-infoWaiting for more information from submitterWaiting for more information from submitter

    on Mar 26, 2019
15. kylecarbs

    added this to the March 2019 milestone on Mar 26, 2019
16. kylecarbs commented on Mar 27, 2019

    

    kylecarbs

    on Mar 27, 2019

    Member

    More actions

    Fixed with the latest release.
17. kylecarbs

    closed this as completedon Mar 27, 2019
18. NGTmeaty commented on Mar 27, 2019

    

    NGTmeaty

    on Mar 27, 2019

    Contributor

    More actions

    Thanks Kyle!