indexeddb: Always consider versionupgrade events to be exclusive - #46610
Merged
Conversation
|
🔨 Triggering try run (#29642114777) for Linux (WPT) |
|
Test results for linux-wpt from try job (#29642114777): Flaky unexpected result (39)
Stable unexpected results that are known to be intermittent (20)
|
|
✨ Try run (#29642114777) succeeded. |
simonwuelker
approved these changes
Jul 19, 2026
| // > ensure that only one connection to the database is open when an upgrade | ||
| // > transaction is live. | ||
| // | ||
| // This mean that versionupgrade transactions are always overlapping with othrs. |
The specification says that `versionupgrade` events should always be exclusive. The previous code was attempting to do that by setting the list of scopes in transaction to all scopes, but that list can go stale is new scopes are added. This extra check ensure that the `versionupgrade` event continues to be truly exclusive. Signed-off-by: Martin Robinson <martin@abandonedwig.info>
mrobinson
force-pushed
the
indexeddb-versionchange
branch
from
July 19, 2026 12:22
7f06667 to
fac0034
Compare
mrobinson
enabled auto-merge
July 19, 2026 12:22
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 specification says that
versionupgradeevents should always beexclusive. The previous code was attempting to do that by setting the
list of scopes in transaction to all scopes, but that list can go stale
if new scopes are added. This extra check ensure that the
versionupgradeevent continues to be truly exclusive.Testing: This greatly decreases the flakiness of the IndexedDB tests for me
when run locally. This should fix three flaky tests on CI and probably more.
Fixes: #44200.
Fixes: #46603.
Fixes: #46123.