AsyncWrap init hook threw
See original GitHub issueSometimes I get the error:
FATAL ERROR: node::AsyncWrap::AsyncWrap init hook threw
Aborted
Node v4.2.4 & trace v2.2.0.
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
async-wrap: no way to catch errors without changing the throw ...
var asyncWrap = process.binding('async_wrap'); // Enable asyncWrap and call init hook function on async initialization var asyncHooksObject ...
Read more >Async hooks | Node.js v19.3.0 Documentation
The callbacks init() / before() / after() / destroy() are called for the respective asynchronous event during a resource's lifetime. All callbacks are...
Read more >AsyncWrap Tutorial - An Introduction - node as we go
Grab the JS hooks to AsyncWrap. var async_wrap = process.binding('async_wrap'); // Setup needed variables and callbacks. var kCallInitHook ...
Read more >A Pragmatic Overview of Async Hooks API in Node.js - ITNEXT
Recently I wrote a post about request id tracing in Node.js apps. The proposed solution was built around cls-hooked library, which in its ......
Read more >Async Hooks in Node.js - GeeksforGeeks
Powerful and flexible API. These resources are tracked in C++ and anything inheriting from the AsyncWrap class is an asynchronous resource. Life ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I have published:
2.2.1
with a better engines field that supports^5.3
2.0.2
with a better engines field that supports^4.0
2.0.2
unfortunately don’t have a fix for #17, that is not possible without the new features.Also, I don’t plan to continue doing legacy updates. But hopefully it shouldn’t be necessary when
4.2.5
gets released.I guess semver was violated to that regard, I’m sorry about that. It is hard to keep track of when
trace
uses node internal API.