vscode-js-debug: Error activating auto attach, please report to https://aka.ms/js-dbg-issue

✗ firebase emulators:start --inspect-functions
Debugger listening on ws://127.0.0.1:56849/df25ac21-1fd9-4af6-8c8b-281d113d9647
For help, see: https://nodejs.org/en/docs/inspector
Error activating auto attach, please report to https://aka.ms/js-dbg-issue
i  emulators: Starting emulators: functions, firestore, hosting
⚠  emulators: It seems that you are running multiple instances of the emulator suite for project [myproject]. This may result in unexpected behavior.
⚠  functions: You are running the functions emulator in debug mode (port=9229). This means that functions will execute in sequence rather than in parallel.
⚠  functions: The following emulators are not running, calls to these services from the Functions emulator will affect production: database, pubsub
⚠  Your requested "node" version "10" doesn't match your global version "14"
⚠  firestore: Did not find a Cloud Firestore rules file specified in a firebase.json config file.
⚠  firestore: The emulator will default to allowing all reads and writes. Learn more about this option: https://firebase.google.com/docs/emulator-suite/install_and_configure#security_rules_configuration.
i  firestore: Firestore Emulator logging to firestore-debug.log
i  hosting: Serving hosting files from: public
✔  hosting: Local server: http://localhost:5000
i  ui: Emulator UI logging to ui-debug.log
i  functions: Watching "/Users/fredriccliver/Projects/[myproject]/functions" for Cloud Functions...
>  Debugger listening on ws://localhost:9229/66cf42da-91f5-4f73-8a9e-69f13b83b215
>  Debugger listening on ws://localhost:9229/66cf42da-91f5-4f73-8a9e-69f13b83b215
>  Debugger listening on ws://localhost:9229/66cf42da-91f5-4f73-8a9e-69f13b83b215
>  For help, see: https://nodejs.org/en/docs/inspector
>  Error activating auto attach, please report to https://aka.ms/js-dbg-issue

My project is based on firebase and I’m using firebase emulator with --inspect-functions option. But, the remote debugging connection has been broken whenever I modified a functions-side(backend) code.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 16 (8 by maintainers)

Most upvoted comments

With the last VSCode delivery, this issue was totally resolved.

fredriccliver on Oct 9, 2020

I fixed one case I happened to run into on OSX https://github.com/microsoft/vscode/commit/c17be0166314d1f83fd10eff380bfe36eca02e56

If this was the issue you were running into, it would also have ‘solved itself’ at some point when the OS cleared your temp directory.

connor4312 on Sep 30, 2020

@yonifra I think that issue should be fixed in the upcoming release of vscode where we simplify connection/server handling logic. Please let me know if not.

@fredriccliver if you’re still able to hit that error I’m made a commit that logs more information about what happens. Please try tomorrow’s nightly build and share the output, which should be more detailed. Note that after updating you’ll have to run your program/node twice to get show the details, since it lazily updated the ‘bootloader’ script on the first run.

connor4312 on Sep 25, 2020

Okay, thank you for the info! I will go ahead and close this since you’re no longer hitting any issues. If you (or anyone else) hits this again, then there should be a more useful error message for us to go on.

Thanks again for you help and willingness in debugging this.

connor4312 on Sep 29, 2020

@connor4312 Thanks Conner, yes I checked your update. I will share the detailed error on here after the nightly build released, 5 PM PST, tomorrow.

fredriccliver on Sep 25, 2020

Ok, thanks. I’ll give the firebase emulator a try on my machine later today.

At the last couple of seconds of the video, I saved the source file, and the remote pipe has been broken.

It looks like you used the “attach to process” command, which will stop once the process is killed. Firebase probably restarts the Node.js process; you can automatically reconnect by creating a launch.json like

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "node",
      "request": "attach",
      "name": "Attach to Process",
      "restart": true,
      "port": 9229,
      "skipFiles": [
        "<node_internals>/**"
      ]
    },
  ]
}

with restart: true, this will reconnect. Then, hit F5 to connect to the process.

connor4312 on Sep 22, 2020