Uh oh!
There was an error while loading. Please reload this page.
node-api: enable uncaught exceptions policy by default - #49313
Merged
nodejs-github-bot merged 2 commits intoSep 25, 2023
Conversation
nodejs-github-bot
commented
Aug 24, 2023
Collaborator
Review requested:
|
nodejs-github-bot
commented
Aug 25, 2023
Collaborator
This was referenced Aug 26, 2023
nodejs-github-bot
commented
Sep 7, 2023
Collaborator
gabrielschulhof
commented
Sep 8, 2023
Contributor
It would be best to land this after #49515. |
This enables the option `--force-node-api-uncaught-exceptions-policy` for a specific Node-API addon when it is compiled with `NAPI_EXPERIMENTAL` (and this would be the default behavior when `NAPI_VERSION` 10 releases). This would not break existing Node-API addons.
legendecasforce-pushed
the
node-api/uncaught-exception
branch
from
September 11, 2023 17:25
2efb890 to
bcda6c4Comparenodejs-github-bot
commented
Sep 12, 2023
Collaborator
Uh oh!
There was an error while loading. Please reload this page.
| const binding = require(`./build/${common.buildType}/binding`); | ||
| const binding = require(`./build/${common.buildType}/test_uncaught_exception`); | ||
| const callbackCheck = common.mustCall((err) => { |
Contributor
There was a problem hiding this comment.
Would it be possible to put this code in a common module? That would make it clear that the same test is supposed to work with both versions, and only the preprocessor flags and the node launch flags differ. I think files not starting with test_ are not executed when the test suite runs.
gabrielschulhof
approved these changes
Sep 22, 2023
nodejs-github-bot
commented
Sep 23, 2023
Collaborator
20 tasks
nodejs-github-bot
commented
Sep 24, 2023
Collaborator
nodejs-github-bot
commented
Sep 25, 2023
Collaborator
Landed in 77597d3 |
21 tasks
ruyadorno pushed a commit
that referenced
this pull request
Sep 28, 2023
This enables the option `--force-node-api-uncaught-exceptions-policy` for a specific Node-API addon when it is compiled with `NAPI_EXPERIMENTAL` (and this would be the default behavior when `NAPI_VERSION` 10 releases). This would not break existing Node-API addons. PR-URL: #49313 Refs: #36510 Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Gabriel Schulhof <gabrielschulhof@gmail.com>
Closed
ruyadorno pushed a commit
that referenced
this pull request
Sep 28, 2023
This enables the option `--force-node-api-uncaught-exceptions-policy` for a specific Node-API addon when it is compiled with `NAPI_EXPERIMENTAL` (and this would be the default behavior when `NAPI_VERSION` 10 releases). This would not break existing Node-API addons. PR-URL: #49313 Refs: #36510 Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Gabriel Schulhof <gabrielschulhof@gmail.com>
Merged
targos pushed a commit
that referenced
this pull request
Nov 27, 2023
This enables the option `--force-node-api-uncaught-exceptions-policy` for a specific Node-API addon when it is compiled with `NAPI_EXPERIMENTAL` (and this would be the default behavior when `NAPI_VERSION` 10 releases). This would not break existing Node-API addons. PR-URL: #49313 Refs: #36510 Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Gabriel Schulhof <gabrielschulhof@gmail.com>
sercher added a commit
to sercher/graaljs
that referenced
this pull request
Apr 25, 2024
This enables the option `--force-node-api-uncaught-exceptions-policy` for a specific Node-API addon when it is compiled with `NAPI_EXPERIMENTAL` (and this would be the default behavior when `NAPI_VERSION` 10 releases). This would not break existing Node-API addons. PR-URL: nodejs/node#49313 Refs: nodejs/node#36510 Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Gabriel Schulhof <gabrielschulhof@gmail.com>
sercher added a commit
to sercher/graaljs
that referenced
this pull request
Apr 25, 2024
This enables the option `--force-node-api-uncaught-exceptions-policy` for a specific Node-API addon when it is compiled with `NAPI_EXPERIMENTAL` (and this would be the default behavior when `NAPI_VERSION` 10 releases). This would not break existing Node-API addons. PR-URL: nodejs/node#49313 Refs: nodejs/node#36510 Reviewed-By: Michael Dawson <midawson@redhat.com> Reviewed-By: Gabriel Schulhof <gabrielschulhof@gmail.com>
This file contains hidden or 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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This enables the option
--force-node-api-uncaught-exceptions-policyfor a specific Node-API addon when it is compiled with
NAPI_EXPERIMENTAL(and this would be the default behavior whenNAPI_VERSION10 releases). This would not break existing Node-APIaddons.
Refs: #36510