What
A WebSocket tunnel that never gets its protocol v2 negotiation acknowledged now fails fast instead of continuing in an undefined state.
Details
- Connecting arms a
helloAckDeadline; if the server does not acknowledge protocol v2 within the open timeout, negotiation fails with "tunnel protocol v2 negotiation failed" and a reason built from the fragment "no HELLO_ACK within" plus the elapsed limit. - An ack carrying an unexpected version is rejected, and the connection is closed with a 502 "Bad Gateway".
- The deadline is cleared both on receiving HELLO_ACK and on teardown.
- A new telemetry event
agent_proxy_request_v2_not_ackedfires on the failure path.
Evidence
requires tunnel protocol v2; the server did not acknowledge the negotiation (, agent_proxy_request_v2_not_acked
Strings lifted out of the shipped bundle, so the claim above can be checked against them.