-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
Some http2
errors are not captured
#28895
Labels
http2
Issues or PRs related to the http2 subsystem.
Comments
https://nodejs.org/dist/latest-v12.x/docs/api/http2.html#http2_settings_object
|
@himself65 I think you have misunderstood me, the error isn't captured at all. It's an unhandled error. |
const tls = require('tls');
try {
const session = tls.connect(443, 'example.com', () => {
throw new Error('Not captured');
});
session.on('error', error => {
console.log('Captured an error', error);
});
} catch (error) {
console.log('Captured an error', error);
} |
3 tasks
Fixed by #28908. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See it on RunKit.
Actual behavior
Expected behavior
Possible solution
It's thrown from here:
node/lib/internal/http2/core.js
Line 975 in 98d8ed6
I think it needs to be like:
The text was updated successfully, but these errors were encountered: