Tim Olson
bc9520f1b1
When send() was called while the socket was still CONNECTING (state 0, not yet OPEN), it queued the message and scheduled a reconnect after 1 second. The socket then connected successfully, but 1 second later the scheduled reconnect fired and closed the working session (code 1005), disrupting any in-flight requests (e.g. get_bars). Two fixes: 1. Don't schedule a reconnect when the socket is CONNECTING — it is already in the process of connecting, no reconnect needed. 2. Cancel any pending reconnect timer in onopen — if a timer was already scheduled before the connection succeeded, clear it. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>