-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Asyncwrap more #5756
Merged
Merged
Asyncwrap more #5756
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
41f333e
src,http_parser: remove KickNextTick call
trevnorris 2dadd89
src: reword command and add ternary
trevnorris f9938b6
async_wrap: setupHooks now accepts object
trevnorris 20337ad
async_wrap: notify post if intercepted exception
trevnorris a17200b
async_wrap: don't abort on callback exception
trevnorris 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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
'use strict'; | ||
|
||
require('../common'); | ||
const assert = require('assert'); | ||
const async_wrap = process.binding('async_wrap'); | ||
var asyncThrows = 0; | ||
var uncaughtExceptionCount = 0; | ||
|
||
process.on('uncaughtException', (e) => { | ||
assert.equal(e.message, 'oh noes!', 'error messages do not match'); | ||
}); | ||
|
||
process.on('exit', () => { | ||
process.removeAllListeners('uncaughtException'); | ||
assert.equal(uncaughtExceptionCount, 1); | ||
assert.equal(uncaughtExceptionCount, asyncThrows); | ||
}); | ||
|
||
function init() { } | ||
function post(id, threw) { | ||
if (threw) | ||
uncaughtExceptionCount++; | ||
} | ||
|
||
async_wrap.setupHooks({ init, post }); | ||
async_wrap.enable(); | ||
|
||
// Timers still aren't supported, so use crypto API. | ||
// It's also important that the callback not happen in a nextTick, like many | ||
// error events in core. | ||
require('crypto').randomBytes(0, () => { | ||
asyncThrows++; | ||
throw new Error('oh noes!'); | ||
}); |
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.
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.
Is there a reason for requiring callers to explicitly disable callbacks, vs implicitly disabling them & restoring them?
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'm missing context. Users have to explicitly run
async_wrap.enable()
before callbacks will be called. This case is to handle:To prevent callbacks from being pulled out from underneath the user while operations may be in flight.
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.
Right, question is why is it the responsibility of the
setupHooks()
caller toenable()/disable()
? i.e., why can't this be done implicitly bysetupHooks()
?Same question follows when the handlers are invoked. We know that if an
init()
callback triggers an async operation, it risks infinite recursion, so why not implicitly disable async callbacks before invokinginit()
?