-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
KV: Panic because sqlite DB is locked #20116
Comments
marvinhagemeister
added
bug
Something isn't working correctly
ext/kv
Related to "Deno.openKv()" API
labels
Aug 10, 2023
I also have this error ocasionally on Ubuntu 22 in a project unrelated to Fresh. On Windows I think I never had it. Not sure if the OS matters though, because they were different machines. |
It's related to do two Deno processes opening the same KV database. cc @losfair |
This was referenced Aug 17, 2023
losfair
added a commit
that referenced
this issue
Aug 17, 2023
Properly handle the `SQLITE_BUSY` error code by retrying the transaction. Also wraps database initialization logic in a transaction to protect against incomplete/concurrent initializations. Fixes #20116.
littledivy
pushed a commit
to littledivy/deno
that referenced
this issue
Aug 21, 2023
Properly handle the `SQLITE_BUSY` error code by retrying the transaction. Also wraps database initialization logic in a transaction to protect against incomplete/concurrent initializations. Fixes denoland#20116.
littledivy
pushed a commit
that referenced
this issue
Aug 21, 2023
Properly handle the `SQLITE_BUSY` error code by retrying the transaction. Also wraps database initialization logic in a transaction to protect against incomplete/concurrent initializations. Fixes #20116.
losfair
added a commit
to losfair/deno
that referenced
this issue
Aug 24, 2023
Properly handle the `SQLITE_BUSY` error code by retrying the transaction. Also wraps database initialization logic in a transaction to protect against incomplete/concurrent initializations. Fixes denoland#20116.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm not able to reliable reproduce this reliably which makes me assume that this is some sort of race condition.
Steps to reproduce
Again, seems to be a race condition so I cannot reliably reproduce this 100% of the time.
fresh-project
deno run -A --unstable dev.ts
deno run -A --unstable dev.ts
again to restart itThe text was updated successfully, but these errors were encountered: