Add connection incident history and hover diagnostics - #102
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Cloud outages currently leave a message over the terminal and little evidence to inspect once connectivity recovers. Move the explanation into a hover/focus/click panel on the connection indicator and retain a downloadable incident history after recovery.
History lasts for the current tab and is cleared on account change. Browser online status is only a hint, and website probes may be served by a service worker. This does not add server-side metrics or persistent telemetry.
Validation: all 254 UI tests pass on latest main;
npx tsc --noEmitandgit diff --checkpass. Tests cover panel interaction, recovery history, probe throttling, credential stripping, history bounds, and socket cleanup. No live outage test performed for these changes.