cmcfarlen opened a new pull request, #13460:
URL: https://github.com/apache/trafficserver/pull/13460

   ## Draft — CI verification
   
   Final batch of last-minute adds for **10.2.0**: the 10 PRs sitting at `For 
v10.2.0` in the
   `ATS v10.2.x` project, cherry-picked with `-x` in master merge order.
   
   | PR | Title |
   |----|-------|
   | #13349 | Support OpenSSL 3.0 APIs for Diffie-Hellman |
   | #13363 | Fix H2 origin payload handling |
   | #13416 | Allow dynamic TLS record sizing |
   | #13423 | Fix Fedora OTEL and WAMR builds |
   | #13429 | doc: clarify run-plugin argument is fixed at load time |
   | #13156 | Add Prometheus v2 labeled stats |
   | #13213 | Add H3 quiche traffic handling tests and provide fixes |
   | #13391 | TSHttpAltInfoQualitySet: add an autest |
   | #13402 | Extend pipeline autest to verify HTTP/1.1 request framing |
   | #13453 | Fix PluginVC server connection cast |
   
   None carry the `Incompatible` label; none were already present on 10.2.x.
   
   ### Adaptations for 10.2.x
   
   - **#13416** — kept 10.2.x's `ssl.session_cache.*` records block; applied 
only the
     validation-range change (`[0-16383]` → `[-1-16383]`) that the fix is about.
   - **#13213** — three small conflicts resolved (`_close_transactions()` in 
the HQSession
     dtor, `_handle_error()` on the read-vio error path, and the SNI test's 
cert setup).
     Its new h3 autests used the `ssl_multicert.yaml` Disk API, which the 
10.2.x autest
     harness doesn't provide; converted `h3_curl` and `h3_go_client` to the flat
     `ssl_multicert.config` form (the other new h3 tests already guard with 
`hasattr`).
   
   ### Testing
   
   Local build clean; `ctest` 162/163 — the single failure is the pre-existing 
macOS-local
   `test_jsonrpcserver` unix-socket flake, unrelated to these picks.
   
   Note this build had QUIC disabled locally, so **CI is the real signal for 
#13213's H3
   changes** (and for the new h3 autests generally).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to