glm-5.3-flash
e023d3275e
Two stateful op-sequence harnesses (fuzz/shared): - ws_session_opseq: the WS byte adapter's generic pumps driven end-to-end over a mock socket flavor through the new byte_adapter::fuzzing drive hub (FuzzMockSocket flavor, FuzzChannels/FuzzWriteSide channel bundle, pump spawn funnels, FuzzInboundChunkProgress). Asserts lossless inbound forwarding (exact after the teardown joins), the WS-01 walk's completed-chunk count vs the declared frame count, the WS-15 close mapping (1002/1011/verbatim-requested + per-cause reasons), lossless write framing onto the declared chunk stream (FWD-21's failure-carry included), lane-failure isolation (the alkcall 0.8.1 class), and pump termination within the bound. - retry_throttle: the inlined RetryAfterMiddleware's throttle map through the new client::fuzzing hub — capacity bound, the expired-first + Farthest-future eviction policy, the ceiling clamp, refresh contraction, the Retry-After parse partition, and the jitter bounds. 16 committed seeds (8 per target) in gen_fuzz_seeds.py, hand-encoded against the arbitrary 1.4.x derive layout with ceiling-division variant tags and per-element keep-going bytes, pinned by seed-decode tests. fuzz/shared gains bytes/futures/tokio/url/ http/httpdate/arbitrary deps. Verification: main crate 441 default tests, fuzz shared replay 21/21 (default + no-default-features), cargo fuzz build clean (5 targets), clippy+fmt clean both crates.
alkhttp fuzzing
cargo-fuzz targets for the HTTP surface's hand-rolled parse paths. The
design and operating rules live in docs/plans/fuzzing.md (adopted
from alkcall's docs/research/fuzzing.md); this README is the
operational cheat-sheet.
Layout
fuzz_targets/— nightly-onlyfuzz_target!binaries (thin wrappers).shared/— stable-toolchain library holding the invariant logic; the corpus replay tests run here on plaincargo test.corpus/<target>/— committed seeds (regenerate withpython3 fuzz/gen_fuzz_seeds.py).artifacts/— gitignored crash/oom/timeout artifacts + campaign logs.
Targets
| Target | Drives |
|---|---|
sse_parser |
SseParser::feed + the FWD-17 envelope mapping (src/adapters/forward.rs) — the SSE frame parser every subscription forwards through |
ws_chunk_framing |
WriteChunkWalk (the write pump's chunk walk) (src/websocket/byte_adapter.rs) |
spec_import |
OpenAPISpec::from_str/from_yaml/from_json, the YAML normalization boundary, CompiledInputSchema compile/harden/validate, FromMCP::build_spec (src/adapters/openapi_spec.rs, input_validation.rs, from_mcp/mod.rs) |
ws_session_opseq |
stateful op sequences over the WS byte adapter's generic pumps (run_read_pump/run_write_pump over the mock socket flavor) — interleavings, close timing, loud-gate mapping, backpressure |
retry_throttle |
the inlined RetryAfterMiddleware's throttle map: capacity bound, eviction policy, ceiling clamp, refresh contraction, Retry-After parse partition |
Running a campaign — always detached
Agent sessions must never run fuzzing in the foreground (an OOM in a target can take down the session host; see docs/plans/fuzzing.md §2). Use the detached runner:
fuzz/run-detached.sh sse_parser
# poll:
tail -n 50 fuzz/artifacts/sse_parser-*.log
ls fuzz/artifacts/sse_parser/
pgrep -f "cargo fuzz run sse_parser"
FUZZ_RUNTIME_SECS=1800 fuzz/run-detached.sh sse_parser for a longer
campaign. The runner pins -fork=1 -rss_limit_mb=2048 -malloc_limit_mb=2048 -timeout=25 and detaches via setsid + nohup.
Corpus replay (the standing fuzz gate)
cargo test --manifest-path fuzz/shared/Cargo.toml
Replays every committed seed through the same invariant functions the fuzzer runs, on stable, no nightly needed. Part of the release verification checklist (AGENTS.md).
Toolchain notes
rust-toolchain.toml pins nightly for this subtree only (llvm-tools
required by cargo-fuzz); the crate itself stays on stable at MSRV 1.88.
cargo fuzz build must be run with the fuzz dir as CWD or trust the
toolchain file (rustup resolves per directory).
Run campaigns before releases and after touching src/adapters/forward.rs
(the SSE parser), src/websocket/byte_adapter.rs (the WS chunk walk),
or the import adapters (src/adapters/openapi_spec.rs,
input_validation.rs, from_mcp/).