Remove the infrastructure tier#1017
Merged
Merged
Conversation
The infrastructure section is not going to be pursued, so this drops it whole rather than leaving eight entries nobody maintains sitting in the rankings. It also retires the pipelined failure it was hiding: apache, caddy, pingora and traefik published rps=0 with 100% 4xx/5xx on a profile that counted toward their composite, and the container logs showed a clean startup with no clue as to why. Removes 8 framework dirs (apache, caddy, envoy, h2o, h2o-h2c, nginx, pingora, traefik), their 73 run logs, and their 75 result rows across site/data. h2o and h2o-h2c shared the display name "h2o"; no display name was mixed across types, so nothing else in the rankings shifts. Safe with respect to the gateway profiles: those compose files build their edge from ./proxy inside the gateway framework's own directory (aspnet-minimal_nginx, aspnet-minimal_caddy, sark-gateway, trillium), not from frameworks/nginx. Frameworks that merely embed one of these servers (frankenphp-trueasync, h2o-mruby, ngx-php, openresty) are separate entries and are untouched. Board: drops the Infra filter pill, its CSS and badge rules, the tooltip and abbreviation entries, the localStorage type whitelist, and the infrastructure branch in isScored. The engine-is-exclusive filter logic stays; only infrastructure leaves it. Generator: drops the infraScored flag from all 28 CATALOG entries and from the emitted profile objects. Docs: deletes implementation-rules/infrastructure.md and its card, and removes the tier from meta-json.md, engine.md and the type-specific scoring section. data.js/docs.js are left alone -- CI regenerates them at deploy from site/data, which this commit purges. current.json is likewise untouched: rebuild_site_data.py regenerates it from the local machine, which would have overwritten the benchmark box's hardware with mine.
MDA2AV
added a commit
that referenced
this pull request
Jul 24, 2026
#1017 removed the infrastructure tier and took the other four type colours with it. All five lived on a single line: .tsq-flagship{...} .tsq-emerging{...} .tsq-experimental{...} .tsq-engine{...} .tsq-infrastructure{...} so deleting "the infrastructure badge rule" deleted the line. Every other removal in that commit was correctly scoped -- the filter pill, the tooltip, the abbreviation, the localStorage whitelist, the isScored branch and .b-infrastructure were all infrastructure-only. This one wasn't, because the line was shared. .tsq kept its width, height and border-radius but lost every background, so each square rendered as a 10x10 transparent box. Both grid renderers still emit `class="tsq tsq-<type>"`, so nothing was wrong with the markup -- there was simply no colour to paint. The yellow tuned ring kept showing because it is a ::after with its own background, which is why the squares looked like they vanished from beside an otherwise intact marker. Restores the four surviving colours at their original values, unchanged and still matching the .b-* badge and filter-pill palette (flagship #2e9e6a, emerging #3b73c4, experimental #d98e2b, engine #cb5f51). One rule per line now, so removing a tier can't silently take the others again. Verified in headless Chrome against the real data files, on this branch and on main for comparison: main this branch flagship + emerging 51/51 transparent 0/51, correct colours engine 26/26 transparent 0/26, rgb(203,95,81) experimental 2/2 transparent 0/2, rgb(217,142,43) Checked in both grid renderers (composite table and profile grid) and in dark mode; the tuned ring still renders.
MDA2AV
added a commit
to Kaliumhexacyanoferrat/HttpArena
that referenced
this pull request
Jul 24, 2026
Resolves the conflict GitHub reported against this PR. Nothing conflicted textually: the PR renames site/static/new-leaderboard/index.html to site/leaderboard/index.html while main modified it in place, and GitHub's mergeability check does not apply rename detection, so it reported the pair as a modify/delete conflict. `git merge-tree --write-tree` exits 0 and both merge directions are clean locally. Carries in the three changes main made to that file since this branch forked at 6bcf729: MDA2AV#1024 the Knowledge Base page search in the left menu (#navq, #navTree, buildSearchIndex) — note buildNav() now clears #navTree, not #nav MDA2AV#1025 the .tsq-* type square colours, which MDA2AV#1017 had deleted by way of a shared CSS line MDA2AV#1018 the type-rules "standard" attribute rename in the generator all of which land in the renamed file and the renamed generator.
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.
Description
The infrastructure section isn't going to be pursued, so this drops it whole rather than leaving eight unmaintained entries in the rankings.
It also retires the failure that section was hiding: apache, caddy, pingora and traefik published
rps=0with 100% 4xx/5xx onpipelined— a profile that counted toward their composite. The container logs show a clean startup and no clue why, so diagnosing it needs a real run on the 64-core box. Removing the tier makes the question moot.Removed
apache,caddy,envoy,h2o,h2o-h2c,nginx,pingora,traefiksite/data/*.jsonh2oandh2o-h2cshared the display nameh2o. No display name was mixed across types, so nothing else in the rankings shifts.Not affected
Gateway profiles are safe. Their compose files build the edge from
./proxyinside the gateway framework's own directory (aspnet-minimal_nginx,aspnet-minimal_caddy,sark-gateway,trillium) — not fromframeworks/nginx. Verified across everycompose.*.yml.Frameworks that merely embed one of these servers are untouched —
frankenphp-trueasync(Caddy),h2o-mruby(builds h2o from source),ngx-php,openresty. They're separate entries with their own tiers.Code changes
infrastructurebranch inisScoredinfraScoredflag from all 28 CATALOG entries and the emitted profile objectsimplementation-rules/infrastructure.md+ its card; removes the tier frommeta-json.md,engine.md, and the type-specific scoring sectionVerification
Regenerated the board from the purged
site/data:flagship: 36, emerging: 37, experimental: 4, engine: 38— 0 infrastructureinfraScoredkeys survivescripts/,.github/,docker/, orframeworks/Notes
data.js/docs.jsdeliberately untouched — CI regenerates them at deploy fromsite/data, which this commit purges.current.jsondeliberately untouched.rebuild_site_data.pyregenerates it from whatever machine runs it — running it here would have replaced the benchmark box's specs (Threadripper 3995WX / 64c / 251Gi / performance governor) with my laptop's. Worth knowing before anyone runs that script off-box.🤖 Generated with Claude Code