mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-25 17:25:57 +03:00
[GH-ISSUE #383] Error saving cipher #222
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#222
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @romain1206 on GitHub (Feb 4, 2019).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/383
[2019-02-04 22:45:47][bitwarden_rs::db::models::user][WARN] Failed to update revision for xxxxxxxx@xxxx.fr
[2019-02-04 22:45:47][bitwarden_rs::error][ERROR] Error saving cipher.
[CAUSE] DatabaseError(
__Unknown,
"database is locked"
)
@dani-garcia commented on GitHub (Feb 4, 2019):
Can you give us some steps to reproduce the error?
@romain1206 commented on GitHub (Feb 5, 2019):
hello,
i have this error when i want move 300 login to another folder.
@mprasil commented on GitHub (Feb 5, 2019):
We do a bunch of updates there in the DB and we also trigger a bunch of update_revision calls (one for each move), maybe we should only trigger one at the end of the operation.
@mprasil commented on GitHub (Feb 5, 2019):
I was thinking that maybe we could defer the revision update and try to compact multiple revision updates into one, but some of the vault functionality actually relies on revision being updated instantly.
I think we can attempt to retry when updating the revision rather than failing straight away. I'll try to implement that.
@mprasil commented on GitHub (Feb 5, 2019):
Okay, I've created a PR, that should hopefully fix this. The revision update should now retry 10 times instead of failing instantly. (similar to attachment updates) I've tried to move about 500 items (as much as Vault let me) and it seems to handle that fine.
@dani-garcia commented on GitHub (Feb 5, 2019):
This hopefully has been fixed with the latest PR. We'll have to wait an hour or so until the docker images are built.
@suricloud commented on GitHub (Mar 18, 2021):
Hi,just installed,and getting this same error?