Skip to content

genhttp-ioxide: build GenHTTP from the branch of Kaliumhexacyanoferrat/GenHTTP#953 - #1783

Merged
MDA2AV merged 2 commits into
mainfrom
genhttp-ioxide-genhttp-branch
Nov 16, 2026
Merged

MDA2AV merged 2 commits into
mainfrom
genhttp-ioxide-genhttp-branch

Conversation

@MDA2AV

@MDA2AV MDA2AV commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

genhttp-ioxide now builds GenHTTP from source: the branch of Kaliumhexacyanoferrat/GenHTTP#953 (update-ioxide-0.20.396) instead of the 11.3.0 release.

What changes

  • Dockerfile: before the restore, it clones GenHTTP at 28b0cd10, the head of [WTX] WebSocket evaluation #953, into /genhttp. It is pinned to that commit because the bench box builds on cached layers: a clone by branch name would keep whichever commit it fetched first. A newer commit means a new GENHTTP_COMMIT.
  • genhttp.csproj: the seven GenHTTP packages become project references into that clone (GenHttpSource, /genhttp by default). The branch's engine pins ioxide 0.26.563, so ioxide.pg and ioxide.timer move from 0.15.251 to 0.26.563 with it. The entry's code builds against them unchanged.
  • Tests/EchoHandler.cs: when the reader rejects a frame, the handler closes the connection with FrameError.CloseStatus, which the branch adds: 1007 for invalid UTF-8, 1009 for a frame that is too large, and 1002 for the other protocol errors.
  • Project.cs: MaxFrameSize(64 * 1024), so the entry accepts frames of up to 64 KiB instead of the 16 KiB default.

What #953 brings

Besides ioxide 0.26.563, the branch adds the websocket protocol checks Autobahn found missing: reserved bits, close frames, UTF-8, and the order of continuation frames. TryReadFrame also no longer splits a fragmented message.

Local results (scripts/spec.sh)

Suite 11.3.0 (bench box) This PR (local)
H/1.1 157/159 157/159
H/2 88/146 107/146
H/3 37/81, server crashed 37/81, server crashed
WebSocket 133/244 244/244 (4 non-strict)

All four suites were measured on this PR's final build. Without MaxFrameSize(64 * 1024), the six WebSocket cases with 64 KiB frames fail (238/244).

validate.sh passes all 122 checks locally.

A chunked body fix on the way

The first version of this PR pinned e3974794, on which validate.sh failed one check: POST /echo chunked 102400B over TLS (:8081) came back short. GenHTTP's chunked body reader read a chunk's length after advancing past it, when the reader may already have reset the segments that length is computed from. ioxide's TLS reader does, so the last read of the body reported more bytes than its buffer held. It is fixed on #953 by 28b0cd10, with a regression test, and this PR now pins that commit.

🤖 Generated with Claude Code

…t/GenHTTP#953

GenHTTP is cloned at e3974794, the head of #953, and referenced as
projects rather than the 11.3.0 packages; the commit is pinned because
the bench box builds on cached layers. ioxide.pg and ioxide.timer move
to 0.26.563 with the branch's ioxide. The echo handler closes a rejected
frame with FrameError.CloseStatus, and frames of up to 64 KiB are
accepted (MaxFrameSize).
@MDA2AV

MDA2AV commented Nov 14, 2026

Copy link
Copy Markdown
Owner Author

/benchmark --save

@github-actions

Copy link
Copy Markdown
Contributor

👋 Benchmark request received. A collaborator will review and approve the run.

@github-actions

Copy link
Copy Markdown
Contributor

Benchmark Results

Framework: genhttp-ioxide | Test: all tests

Test Conn RPS Rate CPU/req p99 p99.9 CPU Mem Δ RPS Δ Mem
baseline 4096 3,550,260 — — — — 6278.6% 2.3GiB +4.2% +4.5%
pipelined 4096 25,258,168 — — — — 6192.3% 2.2GiB +2.3% ~0%
limited-conn 4096 2,661,244 — — — — 6260.7% 3.1GiB +2.0% ~0%
json-comp 4096 638,821 — — — — 6504.5% 2.5GiB +0.9% +4.2%
json-comp 16384 619,159 — — — — 6042.9% 4.1GiB +0.2% -19.6%
json-tls 4096 1,127,765 — — — — 6412.9% 4.9GiB +9.9% -5.8%
8gbit 512 49,258 0.9852 46.85us 127.0us 8676.0us 209.7% 3.6GiB -0.1% ~0%
static-tls 1024 844,729 — — — — 6470.4% 2.4GiB +15.3% -4.0%
async-db 1024 305,792 — — — — 3388.1% 2.1GiB +1.9% ~0%
baseline-h2 256 9,712,147 — — — — 5119.2% 2.2GiB -0.3% ~0%
baseline-h2 1024 9,419,387 — — — — 5378.2% 4.7GiB +5.3% +80.8%
static-h2 256 658,101 — — — — 6456.2% 5.4GiB +17.0% +1.9%
static-h2 1024 602,310 — — — — 6295.5% 13.8GiB +12.4% +2.2%
baseline-h2c 256 9,489,342 — — — — 4970.2% 2.2GiB +0.2% +4.8%
baseline-h2c 1024 9,479,802 — — — — 5373.2% 3.8GiB -2.5% +65.2%
baseline-h2c 4096 9,953,725 — — — — 5638.0% 9.8GiB -0.3% +100.0%
json-h2c 1024 2,059,173 — — — — 6152.9% 3.6GiB ~0% +38.5%
json-h2c 4096 1,968,615 — — — — 6276.1% 11.4GiB +2.7% +67.6%
baseline-h3 64 3,296,413 — — — — 3559.7% 1.1GiB +73.6% -8.3%
static-h3 64 272,124 — — — — 4074.6% 1.6GiB +13.0% ~0%
echo-ws 512 3,572,260 — — — — 6285.4% 2.1GiB -2.6% ~0%
echo-ws 4096 3,687,995 — — — — 6084.6% 2.4GiB -1.5% ~0%
echo-ws 16384 3,233,451 — — — — 5907.9% 5.1GiB -1.0% -1.9%
echo-ws-pipeline 512 40,927,670 — — — — 6427.0% 2.1GiB -9.3% +5.0%
echo-ws-pipeline 4096 41,697,414 — — — — 6376.4% 2.2GiB -9.3% ~0%
echo-ws-pipeline 16384 35,317,267 — — — — 6026.4% 4.5GiB -5.6% +7.1%
echo-ws-limited 512 1,983,788 — — — — 5505.2% 2.1GiB -3.6% ~0%
echo-ws-limited 4096 2,468,273 — — — — 5997.0% 2.5GiB -1.0% +4.2%
latency-1m 1024 997,703 0.9977 23.58us 185.0us 1434.0us 2591.5% 1.9GiB ~0% ~0%
latency-10k 1024 9,982 0.9982 25.80us 104.0us 150.0us 24.6% 1.3GiB ~0% ~0%
latency-500k-8cpu 1024 461,913 0.9238 ⚠️ 17.19us 2749440.0us 2956288.0us 803.9% 502MiB +1.2% -11.0%
async 32000 2,171,269 — — — — 6254.4% 6.9GiB ~0% -22.5%

Composite score, main against this run, in the board's default view:

Family main this run Δ
HTTP/1.1 7116.5 (3 of 107) 7187.0 (3 of 107) +70.5
HTTP/2 3210.5 (2 of 40) 3321.9 (1 of 40) +111.4
HTTP/3 1208.1 (5 of 19) 1593.6 (2 of 19) +385.6
WebSocket 2631.6 (5 of 39) 2531.7 (5 of 39) -99.8

The results on main were measured in another session, so a few points up or down can be the machine and not the change.

Compliance

Suite Tool Score Failed
H/1.1 (h1) http11probe d50d818 157 / 159 2
H/2 (h2) h2spec 2.6.0 108 / 146 (tls 108/146, h2c 108/146) 38
H/3 (h3) h3spec v0.1.15 37 / 81 - the server crashed during the suite 44
WebSocket (ws) autobahn-testsuite 25.10.1 244 / 244 0
H/1.1: 2 failed
Test Expected Got
COMP-OPTIONS-STAR OPTIONS * is the only valid asterisk-form request (RFC 9112 §3.2.4, MUST) 2xx or 405; close/timeout = warn 308, connection left open
SMUG-CHUNK-EXT-INVALID-TOKEN Chunk extension with invalid token character must be rejected (RFC 9112 §7.1.1, MUST) 400 or close 200, connection left open
H/2: 38 failed
Test Expected Got
http2/5.1/2 idle: Sends a RST_STREAM frame GOAWAY Frame (Error Code: PROTOCOL_ERROR) or Connection closed Timeout
http2/5.1/3 idle: Sends a WINDOW_UPDATE frame GOAWAY Frame (Error Code: PROTOCOL_ERROR) or Connection closed Timeout
http2/5.1/5 half closed (remote): Sends a DATA frame GOAWAY Frame (Error Code: STREAM_CLOSED) or RST_STREAM Frame (Error Code: STREAM_CLOSED) or Connection closed WINDOW_UPDATE Frame (length:4, flags:0x00, stream_id:1)
http2/5.1/6 half closed (remote): Sends a HEADERS frame GOAWAY Frame (Error Code: STREAM_CLOSED) or RST_STREAM Frame (Error Code: STREAM_CLOSED) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:1)
http2/5.1/8 closed: Sends a DATA frame after sending RST_STREAM frame GOAWAY Frame (Error Code: STREAM_CLOSED) or RST_STREAM Frame (Error Code: STREAM_CLOSED) or Connection closed WINDOW_UPDATE Frame (length:4, flags:0x00, stream_id:1)
http2/5.1/9 closed: Sends a HEADERS frame after sending RST_STREAM frame GOAWAY Frame (Error Code: STREAM_CLOSED) or RST_STREAM Frame (Error Code: STREAM_CLOSED) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:1)
http2/5.1/11 closed: Sends a DATA frame GOAWAY Frame (Error Code: STREAM_CLOSED) or RST_STREAM Frame (Error Code: STREAM_CLOSED) or Connection closed WINDOW_UPDATE Frame (length:4, flags:0x00, stream_id:1)
http2/5.1/12 closed: Sends a HEADERS frame GOAWAY Frame (Error Code: STREAM_CLOSED) or Connection closed Timeout
http2/5.1.1/1 Sends even-numbered stream identifier GOAWAY Frame (Error Code: PROTOCOL_ERROR) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:2)
http2/5.1.1/2 Sends stream identifier that is numerically smaller than previous GOAWAY Frame (Error Code: PROTOCOL_ERROR) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:5)
http2/5.3.1/1 Sends HEADERS frame that depends on itself GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:1)
http2/5.3.1/2 Sends PRIORITY frame that depend on itself GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed Timeout
http2/5.4.1/1 Sends an invalid PING frame for connection close Connection closed PING Frame (length:8, flags:0x01, stream_id:0)
http2/6.1/2 Sends a DATA frame on the stream that is not in "open" or "half-closed (local)" state GOAWAY Frame (Error Code: STREAM_CLOSED) or RST_STREAM Frame (Error Code: STREAM_CLOSED) or Connection closed WINDOW_UPDATE Frame (length:4, flags:0x00, stream_id:1)
http2/6.3/1 Sends a PRIORITY frame with 0x0 stream identifier GOAWAY Frame (Error Code: PROTOCOL_ERROR) or Connection closed Timeout
http2/6.3/2 Sends a PRIORITY frame with a length other than 5 octets GOAWAY Frame (Error Code: FRAME_SIZE_ERROR) or RST_STREAM Frame (Error Code: FRAME_SIZE_ERROR) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:1)
http2/6.4/1 Sends a RST_STREAM frame with 0x0 stream identifier GOAWAY Frame (Error Code: PROTOCOL_ERROR) or Connection closed Timeout
http2/6.4/2 Sends a RST_STREAM frame on a idle stream GOAWAY Frame (Error Code: PROTOCOL_ERROR) or Connection closed Timeout
http2/6.4/3 Sends a RST_STREAM frame with a length other than 4 octets GOAWAY Frame (Error Code: FRAME_SIZE_ERROR) or RST_STREAM Frame (Error Code: FRAME_SIZE_ERROR) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:1)
http2/6.5/1 Sends a SETTINGS frame with ACK flag and payload GOAWAY Frame (Error Code: FRAME_SIZE_ERROR) or Connection closed Timeout
http2/6.5/2 Sends a SETTINGS frame with a stream identifier other than 0x0 GOAWAY Frame (Error Code: PROTOCOL_ERROR) or Connection closed SETTINGS Frame (length:0, flags:0x01, stream_id:0)
http2/6.5.2/1 SETTINGS_ENABLE_PUSH (0x2): Sends the value other than 0 or 1 GOAWAY Frame (Error Code: PROTOCOL_ERROR) or Connection closed SETTINGS Frame (length:0, flags:0x01, stream_id:0)
http2/6.7/3 Sends a PING frame with a stream identifier field value other than 0x0 GOAWAY Frame (Error Code: PROTOCOL_ERROR) or Connection closed PING Frame (length:8, flags:0x01, stream_id:0)
http2/6.9.1/3 Sends multiple WINDOW_UPDATE frames increasing the flow control window to above 2^31-1 on a stream RST_STREAM Frame (Error Code: FLOW_CONTROL_ERROR) DATA Frame (length:7, flags:0x01, stream_id:1)
http2/8.1/1 Sends a second HEADERS frame without the END_STREAM flag GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed WINDOW_UPDATE Frame (length:4, flags:0x00, stream_id:1)
http2/8.1.2/1 Sends a HEADERS frame that contains the header field name in uppercase letters GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:1)
http2/8.1.2.1/3 Sends a HEADERS frame that contains a pseudo-header field as trailers GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed WINDOW_UPDATE Frame (length:4, flags:0x00, stream_id:1)
http2/8.1.2.2/1 Sends a HEADERS frame that contains the connection-specific header field GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:1)
http2/8.1.2.2/2 Sends a HEADERS frame that contains the TE header field with any value other than "trailers" GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:1)
http2/8.1.2.3/1 Sends a HEADERS frame with empty ":path" pseudo-header field GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed DATA Frame (length:0, flags:0x01, stream_id:1)
http2/8.1.2.3/2 Sends a HEADERS frame that omits ":method" pseudo-header field GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed DATA Frame (length:72, flags:0x01, stream_id:1)
http2/8.1.2.3/3 Sends a HEADERS frame that omits ":scheme" pseudo-header field GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:1)
http2/8.1.2.3/4 Sends a HEADERS frame that omits ":path" pseudo-header field GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed DATA Frame (length:0, flags:0x01, stream_id:1)
http2/8.1.2.6/1 Sends a HEADERS frame with the "content-length" header field which does not equal the DATA frame payload length GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed DATA Frame (length:0, flags:0x01, stream_id:1)
http2/8.1.2.6/2 Sends a HEADERS frame with the "content-length" header field which does not equal the sum of the multiple DATA frames payload length GOAWAY Frame (Error Code: PROTOCOL_ERROR) or RST_STREAM Frame (Error Code: PROTOCOL_ERROR) or Connection closed DATA Frame (length:0, flags:0x01, stream_id:1)
http2/8.2/1 Sends a PUSH_PROMISE frame GOAWAY Frame (Error Code: PROTOCOL_ERROR) or Connection closed Timeout
hpack/4.2/1 Sends a dynamic table size update at the end of header block GOAWAY Frame (Error Code: COMPRESSION_ERROR) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:1)
hpack/5.2/2 Sends a Huffman-encoded string literal representation padded by zero GOAWAY Frame (Error Code: COMPRESSION_ERROR) or Connection closed DATA Frame (length:7, flags:0x01, stream_id:1)
H/3: 44 failed
Test Expected Got
QUIC servers MUST send unexpected_message TLS alert if KeyUpdate in Handshake is received [TLS 6] - predicate failed on expected exception: QUICException / TransportErrorIsReceived ProtocolViolation ""
QUIC servers MUST send unexpected_message TLS alert if KeyUpdate in 1-RTT is received [TLS 6] - predicate failed on expected exception: QUICException / TransportErrorIsReceived ProtocolViolation ""
QUIC servers MUST send no_application_protocol TLS alert if no application protocols are supported [TLS 8.1] - predicate failed on expected exception: QUICException / TransportErrorIsReceived ProtocolViolation ""
QUIC servers MUST send missing_extension TLS alert if the quic_transport_parameters extension is not included [TLS 8.2] - did not get expected exception: QUICException
QUIC servers MUST send missing_extension TLS alert if only the draft quic_transport_parameters extension (0xffa5) is included [TLS 8.2] - did not get expected exception: QUICException
QUIC servers MUST send unexpected_message TLS alert if EndOfEarlyData is received [TLS 8.3] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_FRAME_UNEXPECTED if DATA is received before HEADERS [HTTP/3 4.1] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_MESSAGE_ERROR if a pseudo-header is duplicated [HTTP/3 4.3.1] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_MESSAGE_ERROR if mandatory pseudo-header fields are absent [HTTP/3 4.3.1] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_MESSAGE_ERROR if prohibited pseudo-header fields are present [HTTP/3 4.3] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_MESSAGE_ERROR if pseudo-header fields exist after fields [HTTP/3 4.3] - did not get expected exception: QUICException
HTTP/3 servers MUST treat a request with connection as malformed [HTTP/3 4.2] - did not get expected exception: QUICException
HTTP/3 servers MUST treat a request with keep-alive as malformed [HTTP/3 4.2] - did not get expected exception: QUICException
HTTP/3 servers MUST treat a request with proxy-connection as malformed [HTTP/3 4.2] - did not get expected exception: QUICException
HTTP/3 servers MUST treat a request with transfer-encoding as malformed [HTTP/3 4.2] - did not get expected exception: QUICException
HTTP/3 servers MUST treat a request with upgrade as malformed [HTTP/3 4.2] - did not get expected exception: QUICException
HTTP/3 servers MUST treat a request with te as malformed [HTTP/3 4.2] - did not get expected exception: QUICException
HTTP/3 servers MUST accept TE with trailers [HTTP/3 4.2] - expected: Just () / but got: Nothing
HTTP/3 servers MUST send H3_MISSING_SETTINGS if the first control frame is not SETTINGS [HTTP/3 6.2.1] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_FRAME_UNEXPECTED if a DATA frame is received on a control stream [HTTP/3 7.2.1] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_FRAME_UNEXPECTED if a HEADERS frame is received on a control stream [HTTP/3 7.2.2] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_FRAME_UNEXPECTED if a second SETTINGS frame is received [HTTP/3 7.2.4] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_SETTINGS_ERROR if HTTP/2 settings are included [HTTP/3 7.2.4.1] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_FRAME_ERROR if a SETTINGS frame stops mid-parameter [HTTP/3 7.1] - did not get expected exception: QUICException
HTTP/3 servers MUST NOT stop reading settings at a reserved identifier [HTTP/3 7.2.4.1] - did not get expected exception: QUICException
HTTP/3 servers treats a repeated setting identifier as an error whatever its value [HTTP/3 7.2.4] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_FRAME_UNEXPECTED if CANCEL_PUSH is received in a request stream [HTTP/3 7.2.3] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_FRAME_UNEXPECTED if PUSH_PROMISE is received [HTTP/3 7.2.5] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_ID_ERROR if CANCEL_PUSH names a push ID not allowed [HTTP/3 7.2.3] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_ID_ERROR if MAX_PUSH_ID goes down [HTTP/3 7.2.7] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_ID_ERROR if GOAWAY goes up [HTTP/3 5.2] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_FRAME_ERROR if MAX_PUSH_ID has octets after its push ID [HTTP/3 7.1] - did not get expected exception: QUICException
HTTP/3 servers MUST ignore a frame of unknown type, however long [HTTP/3 7.2.8] - expected: Just () / but got: Nothing
HTTP/3 servers MUST send QPACK_DECOMPRESSION_FAILED if an invalid static table index exists in a field line representation [QPACK 3.1] - did not get expected exception: QUICException
HTTP/3 servers MUST send QPACK_DECOMPRESSION_FAILED if a field line references a dynamic table entry that is not there [QPACK 2.2.3] - did not get expected exception: QUICException
HTTP/3 servers MUST send QPACK_DECOMPRESSION_FAILED if a field line is cut short [QPACK 2.2.3] - did not get expected exception: QUICException
HTTP/3 servers MUST send QPACK_DECOMPRESSION_FAILED if a Huffman string is badly padded [QPACK 4.1.2] - did not get expected exception: QUICException
HTTP/3 servers MUST NOT buffer an over-long frame on a control stream [HTTP/3 7.1] - did not get expected exception: QUICException
HTTP/3 servers MUST send QPACK_ENCODER_STREAM_ERROR if a new dynamic table capacity value exceeds the limit [QPACK 4.3.1] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_CLOSED_CRITICAL_STREAM if a control stream is closed [HTTP/3 6.2.1] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_CLOSED_CRITICAL_STREAM if an encoder stream is closed [QPACK 4.2] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_CLOSED_CRITICAL_STREAM if a decoder stream is closed [QPACK 4.2] - did not get expected exception: QUICException
HTTP/3 servers MUST send H3_CLOSED_CRITICAL_STREAM if an encoder stream ends inside an instruction [QPACK 4.2] - did not get expected exception: QUICException
HTTP/3 servers MUST send QPACK_DECODER_STREAM_ERROR if Insert Count Increment is 0 [QPACK 4.4.3] - did not get expected exception: QUICException

@MDA2AV
MDA2AV merged commit b87a914 into main Nov 16, 2026
4 checks passed
MDA2AV added a commit that referenced this pull request Nov 16, 2026
…s job log) [skip ci]

#1783's run (job 132532753667, 2026-11-14) measured f852765, but its
results commit was refused because 533ae33 reached the branch mid-run,
so main kept genhttp-ioxide's results from #1749.

The 32 result rows are rebuilt from that job's log with the repo's own
<tool>_parse on every run's raw output, the winner picked as benchmark.sh
picks it, and rows written as save_result writes them, then folded in with
rebuild_site_data.merge_results. Every row matches the run's Best line and
the results comment exactly. The one approximation: on the four fixed-rate
profiles cpu_usec is recovered from the logged core-seconds and us/req,
within +-0.003%.

Compliance: H/2 (108/146) and WebSocket (244/244) are rebuilt from the
results comment; H/1.1 and H/3 measured the same as main already had. The
rebuilt file renders back to the posted comment byte for byte. Not
recoverable from the log: the h2c listener's own failure list, WebSocket's
non-strict count, and the run's container logs (site/static/logs keeps
#1749's).
MDA2AV added a commit that referenced this pull request Nov 16, 2026
… be pushed (#1816)

A rejected push used to print 'could not push to fork (permissions)' and
leave the step green, so the results were lost without a word. #1783 lost
its saved run that way: a commit reached the branch while the run was
measuring, and the results push was refused as a non-fast-forward.

Now the step fails, and comments on the PR with the reason: the branch
moved (the numbers are for code it no longer has, so they are not rebased
on top either), or the push was refused (a fork without maintainer edits).
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