Assertion failed: (timeout != -1), function uv__io_poll, file ../deps/uv/src/unix/kqueue.c, line 256. #47241
Description
Activity
It's different from #34633 because I'm fairly sure the error you're seeing is a bug that was introduced in libuv/libuv@e8effd4 and subsequently fixed (if somewhat by accident) in libuv/libuv@42cc412.
That other issue was about an ancient node release that predates both commits by a wide margin.
The fix hasn't made it into any libuv release yet. A v1.45.0 release is planned (libuv/libuv#3887) but will take some time to make it into v16.x.
Since there isn't anything to do for node except wait, I'll go ahead and close this. Thanks for the report.Since there isn't anything to do for node
On second thought, node could disable the
uv_loop_configure(UV_METRICS_IDLE_TIME)calls in node.cc and node_worker.cc until libuv is upgraded.@bnoordhuis That will break the event loop utilization API (https://nodejs.org/docs/latest/api/perf_hooks.html#performanceeventlooputilizationutilization1-utilization2). If this is necessary then I'd recommend only disabling it for systems that use
kqueue.I'm not personally invested in this so I'll just go ahead and close it out.
To summarize: known issue, fix pending libuv upgrade, ETA in the next month or so.
- added a commit that references this issue
on May 24, 2023 - added 3 commits that reference this issue
on Jun 4, 2023 - added 2 commits that reference this issue
on Jul 6, 2023 - added 2 commits that reference this issue
on Jul 6, 2023 - added 6 commits that reference this issue
on Aug 14, 2023 - added a commit that references this issue
on Sep 10, 2023 - added 3 commits that reference this issue
on Sep 11, 2023
Version
16
Platform
MacOS 11
Subsystem
No response
What steps will reproduce the bug?
This happens in our azure devops build pipeline automation
https://github.com/Azure/azure-sdk-for-js/pull/25355/checks?check_run_id=12237694551
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
Seems the same as reported in #34633 and microsoft/azure-pipelines-tasks#13785