fix: read serial frames by wb-mqtt-serial's timeouts, not the JS reply timeout - #98

Merged

evgeny-boger merged 12 commits into

feature/wasm-port-frame-timeouts

Sep 3, 2026

Commits on Sep 1, 2026

fix(port): read frames by wb-mqtt-serial's timeouts, not the JS reply timeout

evgeny-boger
and
claude
committed
5d38613
fix(e2e): run without WebSerial, and keep traces of failed CI runs

evgeny-boger
and
claude
committed
8eaca1d
fix(serial): never reject into Asyncify, and actually close a wedged port

evgeny-boger
and
claude
committed
1a081a6

Commits on Sep 2, 2026

ci(e2e): retry a flaky spec twice on CI instead of failing the build

evgeny-boger
and
claude
committed
ab8b2c3
fix(serial): don't hand ReadChunk the previous reply on the unwind pass

evgeny-boger
and
claude
committed
5c1b90f
fix(port): keep Asyncify side effects inside the async callback

evgeny-boger
and
claude
committed
375f7d4
fix(serial): one long-lived reader, no cancel() per read

evgeny-boger
and
claude
committed
76a8525
fix(rpc): wake the request loop on the reply, not on a 1 ms poll

evgeny-boger
and
claude
committed
ae23928
fix(port): match TSerialPort's send-time rounding and ReadByte's timeout type

evgeny-boger
and
claude
committed
3a8ce38

Commits on Sep 3, 2026

refactor(port): match code style, delete orphan code
u236
committed
f984862
fix(port): wait out the frame, not the gap between USB batches
u236
committed
45eb031
chore: update wb-mqtt-serial
u236
committed
2c0b1d1