You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That happens because we replace all occurrences of the current UID in the keys and values of all buckets with {{CURRENT_UID}}, and it can happen that a timestamp also contains the current UID.
I found that it would require complicating the current code quite a bit to avoid that issue, and since we plan to migrate from bbolt to sqlite soon (which would solve the issue), I suggest we just wait until that.
Is there an existing issue for this?
Describe the issue
We're randomly getting these failures:
This is likely due to the fact we're not replacing properly the timestamp.
Steps to reproduce
No response
System information and logs
No response
Double check your logs
The text was updated successfully, but these errors were encountered: