diff options
| author | Christophe Besson <cbesson@gmail.com> | 2026-09-04 03:23:10 +0200 |
|---|---|---|
| committer | Christophe Besson <cbesson@gmail.com> | 2026-09-04 03:23:10 +0200 |
| commit | 5098e6cb54173b27673f5761ce187d799ba36b30 (patch) | |
| tree | afd6da05673ad3217ebd88e0975a435df34b32ca /docs/WINDOWS-PORT.md | |
| parent | dad2157ada303a45655d2919f62905369525636f (diff) | |
| download | meshbay-5098e6cb54173b27673f5761ce187d799ba36b30.tar.gz | |
fix(node): run on the default Windows event loop (Proactor)
Verified end to end: a live browser peer on Windows connecting to a Windows
node — handshake, index sync, file download and an ffmpeg-transcoded video
stream all work on the ProactorEventLoop. aiortc only hangs on it in the
same-process loopback the tests use, which the repo-root conftest already
handles for the suite.
So the daemon no longer forces the SelectorEventLoop: that fixed
aiortc-in-one-process but broke ffmpeg (no subprocess support on a Windows
SelectorEventLoop). `use_compatible_event_loop()` becomes
`configure_event_loop()` — a no-op unless MESHBAY_NODE_EVENT_LOOP=selector
is set explicitly, as an escape hatch that probably never needs pulling.
This drops the planned "move ffmpeg off the asyncio loop" work.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Diffstat (limited to 'docs/WINDOWS-PORT.md')
0 files changed, 0 insertions, 0 deletions