drop the static profiles from the four entries that fail only static - #1294
Merged
Conversation
From the sweep on #1292. These four fail validation on the static staleness probe and on nothing else, so the entries stay enabled and keep every other profile they publish; they lose static, static-tls and the 21 result keys those produced. fastpysgi-wsgi, uvicorn engine h2o, varnish infrastructure Same treatment #1290 gave the flagship, emerging and experimental entries in this position, applied to the tiers that were left out of it -- with one difference worth stating: for infrastructure this is a real result rather than a formality. h2o and varnish are proxies whose rule explicitly allows open_file_cache and mmap, and they were given a 30s window against the framework tiers' 2s. They still serve the old bytes after it.
Contributor
|
👋 Heads up! This PR modifies the following frameworks:
|
MDA2AV
added a commit
that referenced
this pull request
Aug 24, 2026
Both fail the fragmentation checks against main, independently of anything
unmerged:
frankenphp-trueasync fails four request shapes -- randomized query,
chunked, chunked in two chunks, randomized body
laravel fails POST chunked and chunked in two chunks
A server that cannot reassemble a request split across TCP segments is not
answering the profile it publishes numbers for.
This PR previously also disabled zix-http2, warp, http4s and fastpysgi-asgi.
That was wrong on all four:
zix-http2, warp fail only the TLS checks added in #1292, which is not
merged. The findings are real -- zix-http2 serves a
self-signed Ed25519 certificate instead of the mounted
RSA pair, warp completes TLS 1.0 handshakes -- but the
rule that forbids them is not in force yet, so disabling
them now punishes entries under a rule that does not
exist. Both pass on main today.
http4s failed POST chunked once on the sweep and passes on
main. One flaky observation is not a verdict.
fastpysgi-asgi fails static and only static on main, so it belongs
with the drop-the-profile treatment in #1294, not here.
MDA2AV
added a commit
that referenced
this pull request
Aug 24, 2026
…1295) Both fail the fragmentation checks against main, independently of anything unmerged: frankenphp-trueasync fails four request shapes -- randomized query, chunked, chunked in two chunks, randomized body laravel fails POST chunked and chunked in two chunks A server that cannot reassemble a request split across TCP segments is not answering the profile it publishes numbers for. This PR previously also disabled zix-http2, warp, http4s and fastpysgi-asgi. That was wrong on all four: zix-http2, warp fail only the TLS checks added in #1292, which is not merged. The findings are real -- zix-http2 serves a self-signed Ed25519 certificate instead of the mounted RSA pair, warp completes TLS 1.0 handshakes -- but the rule that forbids them is not in force yet, so disabling them now punishes entries under a rule that does not exist. Both pass on main today. http4s failed POST chunked once on the sweep and passes on main. One flaky observation is not a verdict. fastpysgi-asgi fails static and only static on main, so it belongs with the drop-the-profile treatment in #1294, not here.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
From the full sweep on #1292. These four fail validation on the static staleness probe and nothing else, so the entries stay enabled and keep every other profile they publish — they lose
static,static-tlsand the 21 result keys those produced.fastpysgi-wsgiuvicornh2ovarnishThis is the same treatment #1290 gave the flagship/emerging/experimental entries in this position, applied to the tiers that were outside its scope.
One difference worth stating: for infrastructure this is a real result, not a formality.
h2oandvarnishare proxies whose rule explicitly permitsopen_file_cacheand mmap, and they are given a 30s window against the framework tiers' 2s. They still serve the old bytes after it.Nothing else is touched —
static-h2andstatic-h3are left alone, and every other profile keeps its results.