FA-26569 / HTTP ranges / Member archive
A would-block read does not mean representation EOF · case 04
A would-block read does not mean representation EOF.
Case contract
Return data if nonempty; otherwise wait when blocked, eof when explicit EOF, else idle. The transport never marks blocked and eof simultaneously.
Why this case matters
Range responses combine representation identity, conditional requests, framing, and partial-object state.
One recorded failure
Sample boundary fixtureThis sample comes from the broken implementation of a controlled reproducer.
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| stream-empty-read-would-block fixture 0 | ["eof", ""] | ["wait", ""] | Failed |
MEMBER ARCHIVE
The complete case is available to members.
This record includes three runnable implementations, regression fixtures, execution results, and source hashes.
Member access is invitation-based. Sign in with your invited account to inspect the sources.
Sign in to the archive ↗