atproto relay implementation in zig
zlay.waow.tech
fix fiber GPF writeup: weeks → days, tangled.sh → tangled.org
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
+1
-1
+1
-1
scripts/fiber_gpf_issue.md
+1
-1
scripts/fiber_gpf_issue.md
···
60
60
61
61
## Context
62
62
63
-
We're building an AT Protocol relay ([zlay](https://tangled.sh/zzstoatzz.io/zlay)) that runs ~2,800 concurrent fibers on `Io.Evented`. We've been working around this by building with ReleaseFast, but recently a separate bug (a websocket off-by-one) manifested as a silent SIGSEGV under ReleaseFast for weeks. ReleaseSafe would have caught it immediately as a bounds-check panic with a stack trace.
63
+
We're building an AT Protocol relay ([zlay](https://tangled.org/zzstoatzz.io/zlay)) that runs ~2,800 concurrent fibers on `Io.Evented`. We've been working around this by building with ReleaseFast, but recently a separate bug (a websocket off-by-one) manifested as a silent SIGSEGV under ReleaseFast for days. ReleaseSafe would have caught it immediately as a bounds-check panic with a stack trace.
64
64
65
65
We understand Evented is experimental. Happy to provide more information or test patches.