This repository was archived by the owner on Oct 28, 2026. It is now read-only.
Repository navigation
perf(home): share stale copies and stabilize browser setup - #342
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
A cold location currently waits for a full Home rebuild when the shared public copy is 60–600 seconds old, even though that age is inside the existing stale period. Serve that validated copy with its original timestamp and current time bounds, then start one coalesced background refresh. A transient claim prevents late joined requests from duplicating a fast failed refresh, and an expiry check keeps an aged-out seed from being served.
Browser dependency acquisition also exhausted the CI job after Azure’s Ubuntu mirror took 10m11s to fetch 25.9 MB. A guarded native Rust command selects Canonical’s HTTPS archive in supported Ubuntu APT configurations before the existing Playwright dependency installation. It preserves signing settings, security entries, package suites, dependencies and fonts. The test sequence, assertions, workers, triggers and job caps remain unchanged.
Validation:
cargo xtask check: 781 native tests, native/Wasm Clippy, formatting and licenses pass.cargo xtask module-check: 17 tests and release Wasm pass; Node boundary tests: 24 pass.Cold-load performance and complete normal CI still require validation on this source.