Repository navigation
Deploy verified peer-piece rate observations - #82
Merged
Merged
Conversation
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.
The public player could keep a stale pessimistic peer-rate estimate despite later fast verified pieces. Pin RelaySwarm d4a1235, rebuild its browser bundle and companion worker, and update module cache URLs so visitors receive the verified short-piece observation fix from relayswarm#49.
The new measurement retains the 300 ms / 32 KiB floors, includes wall gaps and verification, and excludes duplicate or rejected responses. The committed WASM binary and public TURN configuration are unchanged. Updated showcase documentation and llms.txt retain the failed prior 330-second sustained-playback result; this bundle does not claim smoother playback or traffic savings before a new published-runtime check.
Validation: complete site build and all 371 site tests passed; the exact-source bundle receipt and notices were regenerated using installed dependencies and the committed WASM, without a Rust build. Deployed asset readback and the fresh public sustained check follow deployment.