Dylan Conway 88afcf7816 test(integration): use async spawn so the in-process proxy can respond ...

The integration tests run sandboxed curl commands against the HTTP/SOCKS
proxy that lives in the same process. Driving them with spawnSync blocks
this event loop for the duration of the wrapped command, so the proxy
request handler cannot run — curl is waiting on a server whose JS thread
is parked inside the very spawnSync that is waiting for curl. The suite
only passed because some bun versions happen to let the loop tick during
spawnSync; on linux/x86-64 that has been intermittent (the recent CI
flakes), and on newer bun it stops entirely.

Replace spawnSync with a small async spawnAsync helper that mirrors the
{stdout, stderr, status, signal} return shape. The event loop stays
alive, the proxy responds, and reset() between describes no longer hits
its 5s fallback.

Also bump CI bun to 1.3.13.

2026-05-05 12:25:39 -07:00

..

integration-tests.yml

test(integration): use async spawn so the in-process proxy can respond

2026-05-05 12:25:39 -07:00

release.yml

Bake BPF filter into apply-seccomp, build in CI (#199)

2026-04-02 10:58:33 -07:00