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

   Cherry-picks for the 10.2.1 release, taken from the PRs at status `For 
v10.2.1`
   in the `ATS v10.2.x` project. Applied in master merge order.
   
   | PR | Subject | Notes |
   |---|---|---|
   | #13538 | Fix records_yaml startup lookup race | clean |
   | #13510 | doc: rate_limit uses max_age, not max-age | clean |
   | #13238 | prefetch: move cache key acquisition to CACHE_LOOKUP_COMPLETE | 
clean |
   | #13580 | compress: add Vary to cached client responses | clean |
   | #13506 | Per upstream server connection metrics via hidden and derived 
metrics | conflict resolved (see below) |
   | #13577 | Fix silently dropped Streams.all autest assertions | clean |
   
   ### #13506 conflict resolution
   
   `include/proxy/http/OverridableConfigDefs.h` and `include/ts/apidefs.h.in` 
conflicted
   because master carries `HTTP_CACHE_MAX_STALE_AGE_PERCENT` /
   `TS_CONFIG_HTTP_CACHE_MAX_STALE_AGE_PERCENT`, which does not exist on 
10.2.x. Only the two
   entries the PR actually adds were taken:
   
   - `HTTP_PER_SERVER_CONNECTION_METRIC_ENABLED`
   - `HTTP_PER_SERVER_CONNECTION_METRIC_AGGREGATE`
   
   Both are appended immediately before `TS_CONFIG_LAST_ENTRY`, so the plugin 
API enum stays
   backward compatible. Every other file in this pick matches the upstream diff 
byte for byte.
   
   This pick builds on #13505, which is already on 10.2.x.
   
   ### Local verification
   
   - `cmake --build build-autest -- -k 0` — clean
   - `ctest -j4` — 166/167 pass; only `test_jsonrpcserver` fails, a known 
macOS-local
     unix-socket/restart timing issue, not a regression from these picks.
   
   ### Not picked
   
   Six other items are at `For v10.2.1` but their PRs are still open, so there 
is nothing to
   pick yet: #12825, #13063, #13086, #13196, #13355, #13450.
   


-- 
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