Michaël Zasso
Michaël Zasso
`out/Release/node path/to/jest/cli.js`
It seems to me that the goal here is to pass some information to the publisher, rather than preventing other subscribers from receiving the message (which I think depends on...
> it's a general concept that shouldn't need specific handling `try / catch` is a specific handling
> would this mean something like an AbortController in the end ? Maybe. I don't really care about what it is in the end. What bothers me is the fact...
@mscdex I think these issues will be fixed if you rebase.
What use case would be solved by this that cannot work with `setImmediate` ? ```js import { setImmediate } from 'timers/promises'; await setImmediate() ````
The commit fixing the above V8 issue is in V8 9.4. I'll probably open a PR upgrading to that version next week.
I think the root V8 bug is now chromium:1238312. There was recent activity on this CL: https://chromium-review.googlesource.com/c/v8/v8/+/3172764
I added support for `chromium:` expansion.
Pull requests are still welcome.