Open WilliamAndreu opened 3 months ago
Thanks for opening the issue. If you could share any details on how to reproduce, it would be much appreciated. Is this something consistently blocking you, or is it something you saw e.g. once or twice on prod and not on dev?
/cc @nodejs/workers
For reference, the failing assert is: https://github.com/nodejs/node/blob/a407d1f0b3669cc82c755700f0d500fb27cc39ea/lib/internal/worker.js#L354
@aduh95 Hi, the error occurs when using jest with angular 17, when I run the jest command to start the tests I usually get this error, I don't know if it can be related to zone.js.
I got the same error with angular 18 and jest 29 when I run tests with jest --no-cache option.
Version
20.15.1
Platform
Subsystem
No response
What steps will reproduce the bug?
No response
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior? Why is that the expected behavior?
No response
What do you see instead?
Additional information
No response