Repository navigation
Keep crossing wait pages refreshed while open - #111
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
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.
Comparison and crossing pages kept their first wait-time snapshot while open, and optional FX/southbound requests could delay all current waits. They now share the dashboard's five-minute refresh lifecycle, refresh on tab return/reconnection, and reuse the last good reading immediately during route navigation. Comparison also has an English/Spanish refresh control.
The data service deduplicates simultaneous refreshes and publishes current waits before optional feeds. The service worker leaves the live endpoint to Vercel's existing CDN cache and the client's timestamped fallback. The five-minute CDN policy and daily history/FX publication remain unchanged.
Migration notes now record the verified Vercel/IONOS cutover, preserved Pages rollback, and pending two scheduled publication observations/first-week cost review. No new monitoring automation or service is added.
Validation: production build, 8 refresh regressions, 36 source/publication/trust/hours/MDX tests, dependency audit and bundle gate passed locally. Browser verification uses a controlled local comparison feed; complete route and growth checks run in CI.