-
Notifications
You must be signed in to change notification settings - Fork 94
feat: add visibilitychange probe for proactive IDB health check #788
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
leshniak
wants to merge
12
commits into
Expensify:main
Choose a base branch
from
callstack-internal:fix/idb-visibilitychange-probe
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+585
−28
Open
Changes from all commits
Commits
Show all changes
12 commits
Select commit
Hold shift + click to select a range
6569dc7
fix: add IDB backing store corruption healing mechanism
leshniak a2c8ea7
fix: guard stale dbp reject handler, document concurrent budget drain
leshniak 213480b
fix: align comments and logs with actual behavior (drop cache, not cl…
leshniak 1bb21b2
refactor: simplify error type checks per review feedback
leshniak 7633f32
feat: extend IDB heal to detect Safari connection lost error
leshniak 1f14374
refactor: DRY error classification and promise cleanup in createStore
leshniak 8bc7cd4
fix: improve diagnostic logging for all heal and error paths
leshniak fccdb4a
style: fix Prettier formatting in createStoreTest
leshniak 3fbb657
fix: downgrade heal attempt logs from logAlert to logInfo
leshniak a4ebed8
feat: add visibilitychange probe for proactive IDB health check
leshniak 74d04d6
fix: improve diagnostic logging for probe and all heal paths
leshniak b63de8b
fix: move probe healthy log to req.onsuccess to avoid false positive
leshniak File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When the tab becomes visible while
dbpis still a pendingindexedDB.open()and that open later rejects (for example with the same backing-store or connection-lost errors handled below), this separateprobePromise.then(...)chain rejects without any rejection handler. The original store operation may catch its own chain, but the promise returned by thisthenis ignored, so browsers can emit an unhandled rejection during foregrounding; add a rejection handler/catch for the probe path.Useful? React with 👍 / 👎.