Skip to content

fix(wire): restore dispatch read timeout from 10s to 90s - #104

Merged
blaspat merged 1 commit into
mainfrom
fix/dispatch-read-timeout
Aug 4, 2026
Merged

fix(wire): restore dispatch read timeout from 10s to 90s#104
blaspat merged 1 commit into
mainfrom
fix/dispatch-read-timeout

Conversation

@blaspat

@blaspat blaspat commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Summary

The E2E refactor (#103) accidentally changed the dispatch read deadline from 90 seconds to 10 seconds. The server sends pings every ~30s, so connections died before the first ping arrived.

Root cause

readE2E/writeE2E hardcoded 10*time.Second instead of using the configurable timeout the old readOne used (DefaultPongTimeout + 30s = 90s).

Fix

Add readTimeout and writeTimeout fields to Client (90s/10s defaults, matching the pre-E2E dispatch values) and wire them into readE2E and writeE2E.

The E2E refactor in #103 replaced dispatch.ReadOne's 90s deadline
(DefaultPongTimeout + 30s) with readE2E's hardcoded 10s ReadMessage
deadline.  The server sends pings every ~30s, so connections died
before the first ping.

Add readTimeout/writeTimeout fields to Client (90s/10s defaults,
matching the pre-E2E dispatch values) and wire them into readE2E
and writeE2E.

Signed-off-by: Blasius Patrick <blasius.patrick@gmail.com>
@blaspat
blaspat merged commit c7b022e into main Aug 4, 2026
14 checks passed
@blaspat
blaspat deleted the fix/dispatch-read-timeout branch August 4, 2026 13:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant