[Bug] VFS IDBBatchAtomicVFS has error in locks
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, sqlite, wasm
Research direction
Start by reproducing the reported lock error with IDBBatchAtomicVFS in a SharedWorker, using the attached example as the starting point. Compare the behavior with the OPFS VFS and determine whether the failure is specific to this project or upstream; done means the cause and a reproducible result are documented.
Written by the indexing model from the issue text.
Description
When I switched from OPFS VFS into IDBBatchAtomicVFS, the weird bug happen
So I'm curious this is upstream bug ? Which one VFS you commonly use ?
FYI : I ran IDBBatchAtomicVFS in SharedWorker (I want to switch IDBBatchAtomicVFS because OPFS can't run in SharedWorker)
- Dominant language
- JavaScript
- Stars
- 40
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100