READ BYTES · FRAME EVENTS · CONSUME
Stream failure: distinguish partial output from completion
Fragment real encoded bytes, inspect the parser buffer and follow complete events into an ordered text consumer.
Text source and visible output
Appended output
Unparsed buffer: first 32 bytes in hex
Your experiment
Truncate the final three bytes. Inspect the remaining parser buffer and compare partial visible output with the original event fixtures. No silent completion is allowed.
The text is split into six-code-point deltas, numbered from 1. A source fault targets event 3, or the last event when fewer than three exist. Output is appended only after a complete frame is parsed and consumer processing finishes.
In streaming mode a full application queue pauses reads; one additional event may be processing. In buffered mode all body bytes arrive before parsing begins. The same 60-second inspection maps proportionally to each scenario’s modeled duration; it is not a network performance measurement.
Recent parser and consumer events
Original event fixtures
Offline byte-framing lesson. SSE parsing supports only the generated LF-delimited id/data subset; this is not a complete EventSource implementation. The alternative uses a zero compression byte plus four-byte big-endian payload length and UTF-8 JSON, not Protobuf. No HTTP/2 frames, headers, trailers, grpc-status, compression, TLS, provider API, A2A envelope, retries or reconnect/resume are implemented. The queue policy is application backpressure, not transport flow control. Duplicate suppression and strict contiguous event IDs are explicit application policies, not guarantees supplied by SSE/gRPC. Missing IDs are rejected without reordering or replay. Empty source is complete with no output; an incomplete frame remains truncated. SSE specification · gRPC message framing.
Partial text is not a completed answer
Receiving some text does not establish that the final event arrived or that all earlier sequence identifiers were applied. This fixture calculates completion from reconstructed output, expected original events, rejected records and leftover parser bytes. It retains partial output so a reader can inspect what was actually applied. A failure therefore remains visible rather than being hidden by a final caption. The source is local and deterministic; the lab does not call an ADK agent or claim to reproduce all of its finish reasons.
Control the byte and application boundaries
Local text supplies the payload, with the browser limiting entry to one hundred twenty UTF-16 code units. The model groups Unicode code points into records of up to six, each with a sequence identifier and delta string. Framing format selects the LF-delimited SSE subset or an uncompressed five-byte gRPC-style prefix around JSON. Application consumption either parses complete events incrementally or waits for the full body. Bytes per read changes fragmentation, Read interval changes scheduled arrival spacing, Processing per event changes consumer time, and Queued events bounds waiting records separately from the one active record. Parameter edits rebuild the scenario and start inspection unless reduced motion is requested.
Contrast truncation with a sequence gap
Keep a source long enough for several events. Choose Truncate final three bytes and inspect the final state: bytes remain in the decoder and the result is truncated. Change the fault to omit an event identifier. Framing can now finish with no incomplete bytes, but a missing sequence causes later events to be rejected and leaves partial output. Malformed JSON is a third path: a complete frame fails validation and can create a subsequent sequence gap. Compare the pending-byte hex and recent trace, not just the displayed text length.
Inject failures and inspect safely
Source event fault repeats, omits or corrupts the third event, or the last available event for a shorter source; truncation removes the final three wire bytes. Ignore already-applied event IDs affects duplicate records only. Missing or malformed records can leave a sequence gap, and later records are rejected rather than reordered or replayed. Play and Pause inspect sixty seconds of viewing time; Next event advances a recorded scheduler transition; Restart inspection rewinds; Speed adjusts viewing pace; Inspection time scrubs. Visible output, pending-byte hex and recent events reflect the inspected prefix. The complete-run preview and original event list describe the full scenario, not work already consumed.
Test the empty stream and duplicate policy explicitly
Clear Local text and select no fault. There are zero original events and no fabricated appends; the empty output is complete and first-output time remains unavailable. Restore a multi-event source and repeat an event. With duplicate suppression enabled, the repeated frame is decoded but not applied twice. Disabling suppression changes the visible answer and reports duplicate output. A duplicate policy alone cannot repair an omitted event. The model has no persistence, retry, timeouts, provider error envelopes or resume token. Its checks identify a local parser/consumer failure boundary, not recovery behavior for a production service.