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
Someone needs to tell the cache that two separate operations are to be performed atomically. If you rely on the write lock on SQLite, this issue still remains, as the write lock will not trigger during the query operation (it is read-only), allowing two separate processes to both simultaneously create and try to add a non-existing resource... I'll see how I can work around it.
Activity
lshep commentedon Oct 3, 2022
There is a built in locking system on the cache that should prevent this.
romanzenka commentedon Oct 17, 2022
Someone needs to tell the cache that two separate operations are to be performed atomically. If you rely on the write lock on SQLite, this issue still remains, as the write lock will not trigger during the query operation (it is read-only), allowing two separate processes to both simultaneously create and try to add a non-existing resource... I'll see how I can work around it.
hpages commentedon Oct 12, 2023
@romanzenka FYI we're resuming this conversation here.