Repository navigation
port today's keyed work to dev, which is the branch the worker builds - #2903
Merged
Merged
Conversation
Everything from the connection-reuse incident landed on main: the two-arm harness (#2896), the cold recording rules (#2899) and the cold-start cohort on the nine keyed specs (#2902). The materialise worker clones DEV at build time, so none of it can reach a page until the specs exist here. That is why ?tier=keyed-cold currently serves the public provider list: the worker's snapshot predates the new tier and falls through to the default cohort. Same content as main: 9 specs the keyed-cold cohort, 36 provider clones on the cold metric probe.go warm and cold transports, alternating, plus the gated conn trace metrics.go rpc_latency_cold_milliseconds and its histogram rules ocb:rpc_latency_cold_milliseconds:{p50,p90,p99,mean}_24h pnpm validate 246 specs, go build clean. After this merges the worker still needs a rebuild, and there is roughly a 72-minute display floor before the pages show it.
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
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.
port today's keyed work to dev, which is the branch the worker builds
Everything from the connection-reuse incident landed on main: the two-arm
harness (#2896), the cold recording rules (#2899) and the cold-start cohort on
the nine keyed specs (#2902). The materialise worker clones DEV at build time,
so none of it can reach a page until the specs exist here. That is why
?tier=keyed-cold currently serves the public provider list: the worker's
snapshot predates the new tier and falls through to the default cohort.
Same content as main:
9 specs the keyed-cold cohort, 36 provider clones on the cold metric
probe.go warm and cold transports, alternating, plus the gated conn trace
metrics.go rpc_latency_cold_milliseconds and its histogram
rules ocb:rpc_latency_cold_milliseconds:{p50,p90,p99,mean}_24h
pnpm validate 246 specs, go build clean.
After this merges the worker still needs a rebuild, and there is roughly a
72-minute display floor before the pages show it.