-
Notifications
You must be signed in to change notification settings - Fork 8
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
Caught uncaught exceptions #198
Open
Christian-Holbrook
wants to merge
24
commits into
master
Choose a base branch
from
caught-uncaught-exceptions
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 21 commits
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
6b658ce
Add support for breaking on caught or uncaught exceptions
Christian-Holbrook 0dfdf64
WIP, displaying the caught and uncaught exceptions
Christian-Holbrook d4d669f
Add unit tests for the new exceptions breakpoints
Christian-Holbrook ce4728e
Piped through to pass exceptions filters to the debug client
Christian-Holbrook 39a12ec
Some fixes and tweaks
TwitchBronBron 964b4e9
Fix lint issues
TwitchBronBron b9c7a34
Lift some responses to vars for better debugging
TwitchBronBron abb9238
Guard agaist setting exception breakpoints when not supported on the …
Christian-Holbrook edec32d
Fix incorrect init flow for exception breakpoints
TwitchBronBron ecd206a
Fix some lint issues
TwitchBronBron dc49429
Merge branch 'caught-uncaught-exceptions' of https://github.com/rokuc…
TwitchBronBron 3e2aaa8
Add unit tests, and state to track when a debug session is persists b…
Christian-Holbrook 70e5231
Rename any "exceptionsBreakpoints" to exceptionBreakpoints
Christian-Holbrook 4551d78
Add more unit tests
Christian-Holbrook de0b916
Revert some `file:/` package dependencies
TwitchBronBron 3fcca83
Add eslint as a recommended extension
TwitchBronBron 035f87b
Fix lint issues
TwitchBronBron b19bfaa
Fix heap overflow issue
TwitchBronBron c747e3e
Fix most of the broken unit tests
Christian-Holbrook 1bdc4b3
Fix unit test
Christian-Holbrook ee3f80b
Try increasing heap allocation
Christian-Holbrook ce17dda
Revert "Try increasing heap allocation"
Christian-Holbrook fa5aca2
Roll back all package.json changes, deleted node_modules/ and ran $ n…
Christian-Holbrook 353f5eb
Revert package.json to master
Christian-Holbrook File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,5 @@ | ||
{ | ||
"recommendations": [] | ||
"recommendations": [ | ||
"dbaeumer.vscode-eslint" | ||
] | ||
} |
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wouldn't do this. The problem is most likely that you upgraded something in the package-lock (did you perhaps run
npm audit fix
? That does it sometimes).There's a package in there somewhere that isn't happy with the current node version.
Can you roll back the package-lock, delete node_modules, and run
npm install
again?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried to "manually" revert back to the original package.json and commit the newly generated package-lock.json. This caused some other errors where the dependencies were missing some exported functions.
I ended up just running
git checkout master -- package.json package-lock.json
and committed that. That should roll back all the changes on this branch to master for any package*.json changes.The first run of checks failed because 1 unit tests did not pass on the ubuntu CI. I reran it and all the tests pass.
Have you had trouble with the test show in the attached screenshot?