René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"executionAsyncId doesn't return expected value in context of process.on('unhandledRejection')","articleBody":"Version: 12.0.0-pre (78162ad570bfb991e2416c7850be546848a6fcc0)\r\nPlatform: Darwin geegaw.local 18.2.0 Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64 x86_64\r\nSubsystem: async_hooks\r\n\r\nhttps://gist.github.com/isaacs/1f8c5092ba7d67d9a5f4e342ff7778b7\r\n\r\nI am building a domain-like implementation to catch errors using async_hooks.  However, the executionAsyncId is reset to 0 on an `unhandledRejection` event, making it impossible for me to know if I ought to handle the error or crash.\r\n\r\nThe weird thing is that it only fails in this way when the promise rejection is within an async hop, such as a setTimeout.  If the promise rejection happens at the top level, then I get the expected value of `1` as the executionAsyncId.\r\n\r\nThis is preventing me moving node-tap off of core domains.  Fewer modules using domains means that it could be deprecated sooner :)","author":{"url":"https://github.com/isaacs","@type":"Person","name":"isaacs"},"datePublished":"2019-03-20T01:48:33Z","url":"https://github.com/nodejs/node/issues/26794"}