docs(ide): document "IndexedDB database 'vscode-web-db' is closed" error - #88
Draft
iamseeley wants to merge 1 commit into
Draft
docs(ide): document "IndexedDB database 'vscode-web-db' is closed" error#88iamseeley wants to merge 1 commit into
iamseeley wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
2 participants
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 Sentry issue (
Unable to write file 'vscode-log:/…/window.log' (Error: IndexedDB database 'vscode-web-db' is closed.), culpritr1t.writeFileindist/out/vs/code/browser/workbench/workbench.js) originates from the VS Code Web workbench bundle served byide.membrane.io. That bundle is not part of this repository — this repo only contains the Astro docs site, so no code path here produces or handles the failing log flush.The closest correct change available here is documentation: the IDE guide now has a Troubleshooting section explaining the error, its common causes (multiple IDE tabs where one loads a newer version and triggers an IndexedDB
versionchange, site data cleared/evicted while the IDE is open, private browsing), and the remedy (reload the tab; keep one IDE tab per profile).To actually stop the unhandled rejection from being reported, the fix belongs in the IDE/workbench repo: the browser log flush should catch write failures when the IndexedDB connection is closed (or the IndexedDB filesystem provider should reopen the database) instead of rejecting unhandled.
Sentry: https://membrane-io.sentry.io/issues/7090529531/
Anthropic session: sesn_01M1H12iWkWZM33ARGrFd28D