You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b8a873e
Browse filesBrowse the repository at this point in the historyBrowse files
fix: use inactivity timeout for watch instead of whole-request timeout
Watch.watch() passed AbortSignal.timeout(requestTimeoutMs) to fetch, which
counts from request start and stays armed while the response body streams. Any
watch, healthy or not, was therefore aborted with a TimeoutError after 30s.
Replace it with a resettable timer on the AbortController: it is armed before
the fetch (connect timeout), then re-armed on the 200 response and on every
body chunk, so requestTimeoutMs now means "max time without data". The timer is
unref'd and cleared when the watch is done. No public API change.
Also reset ListWatch's reconnectDelayMs to 0 in the TimeoutError branch of
doneHandler. A client-side timeout means we already waited the full request
timeout, so reconnecting immediately cannot tight-loop, while backing off would
leave quiet resources unwatched for up to MAX_RECONNECT_DELAY_MS. Exponential
backoff still applies to real errors and server-side disconnects.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012eAdChkTVkV5KHSedtsML4
0 commit comments