mirror of
https://github.com/vercel/flags.git
synced 2026-09-19 03:49:23 +08:00
283997cf41
The stream reconnect path was aborting the fetch signal when the ping
watchdog fired, which surfaced as `AbortError` on instrumented fetch
spans (e.g. via `@vercel/otel/fetch`) and got reported by APM/error
tracking even though it's an expected reconnect.
Now the watchdog cancels the body reader instead. The read loop exits
via `{ done: true }` and the fetch span closes cleanly. Reconnect
behavior is unchanged.