mirror of
https://github.com/openclaw/openclaw.git
synced 2026-07-09 15:49:40 +08:00
7c0d11eac1
* fix(gateway): don't over-claim a crash on a 1006 abnormal close A 1006 close code means abnormal closure with no close frame, most often a connection dropped under a burst of concurrent tool calls or event-loop saturation — the gateway process typically stays healthy. The troubleshooting text listed "Gateway crashed or was terminated unexpectedly" as a co-equal cause, so an operator could pattern-match it and restart a healthy gateway. Lead with the actionable dropped-under-load cause and demote the unreachable/terminated case to "rare; confirm it is still running". Addresses ask 3 of #100941. The connection-pooling and concurrency-cap asks are architectural and intentionally out of scope, so this does not auto-close the issue. Refs #100941 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(gateway): keep 1006 diagnostics cause-neutral --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: Vincent Koc <vincentkoc@ieee.org>