Files
jambonz-feature-server/test
Ben Younes 74510b0bef fix: retry ws opening-handshake timeout under the default ct policy (#1565) (#1576)
The ws v8 library throws a plain Error('Opening handshake has timed out') with no
.code and name 'Error' when the handshake timeout (JAMBONES_WS_HANDSHAKE_TIMEOUT_MS,
default 1500ms) elapses. BaseRequestor._shouldRetry classified retryable errors only
by .code/.name/.statusCode, so this error matched neither the ct nor rt bucket and was
never retried under the default rp=ct policy — the call failed immediately on the first
attempt, silently bypassing maxReconnects.

Match the handshake-timeout message in the ct bucket so a transient slow WS upgrade
(e.g. a serverless/edge backend cold start) is retried as intended. Adds tape coverage
for both the default-ct retry path and the rp=4xx no-retry path.
2026-09-13 11:49:40 +01:00
..
2025-06-28 15:01:09 -04:00
2025-06-28 15:01:09 -04:00
2023-06-03 08:16:05 -04:00
2020-01-07 10:34:03 -05:00
2023-12-28 14:59:59 -05:00
2023-06-03 09:09:49 -04:00
2023-06-09 14:54:53 -04:00
2023-06-03 08:16:05 -04:00
2023-02-06 08:06:41 -05:00