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

Node v8.5.0 breaks the "uncaught exception" setting #34593

Closed
samrg472 opened this issue Sep 18, 2017 · 4 comments
Closed

Node v8.5.0 breaks the "uncaught exception" setting #34593

samrg472 opened this issue Sep 18, 2017 · 4 comments
Assignees
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@samrg472
Copy link

  • VSCode Version: 1.17.0-insider (b0c0634)
  • OS Version: MacOS 10.13 Beta (17A362a)
  • Node Version: 8.5.0

Using the same sample code from #1746

function failingFunc() {
  return (undefined as any).nope();
}

let promise = new Promise((resolve, reject) => {
 resolve(failingFunc());
});

promise.then(v => {}).catch((e: Error) => {
  console.log(e.message);
});

"Uncaught exceptions" is disabled, however it keeps breaking, regardless if it checked or unchecked.

screen shot 2017-09-18 at 2 39 48 pm

Reproduces without extensions: Yes

@vscodebot vscodebot bot added the insiders label Sep 18, 2017
@ramya-rao-a ramya-rao-a added the debug Debug viewlet, configurations, breakpoints, adapter issues label Sep 18, 2017
@samrg472
Copy link
Author

I was able to confirm this in the stable version of VSCode as well. I checked whether node was the cause and it looks like it is. Switching to node v8.4.0 no longer has this issue.

@samrg472 samrg472 changed the title VSCode ignores the "break on uncaught exception" setting Node v8.5.0 breaks the "uncaught exception" setting Sep 18, 2017
@weinand weinand assigned roblourens and unassigned weinand Sep 18, 2017
@roblourens
Copy link
Member

I can repro as well, with something as simple as

console.log('before');
Promise.reject(new Error('error'))

This is a Node bug, I filed nodejs/node#15464

@roblourens roblourens added the upstream Issue identified as 'upstream' component related (exists outside of VS Code) label Sep 19, 2017
@roblourens
Copy link
Member

You can workaround it in VS Code with

"skipFiles": [ "<node_internals>/**" ]

in your launch config

@chrmarti chrmarti removed the insiders label Sep 27, 2017
@MattMorgis
Copy link

The fix for this landed in be2a5b3 and will be released in Node v8.7.

The corresponding nodejs/#15464 is closed, so probably safe to close this too? Just wanted to help clean up 👍

@samrg472 samrg472 closed this as completed Oct 8, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 22, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

6 participants