-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Address Datastore thread-safety issues #87
Labels
kind/bug
A bug in existing code (including security flaws)
Comments
btc
changed the title
Make datastores thread-safe
Address Datastore thread-safety issues
Sep 17, 2014
I beleive that the mutex wrapped datastore solves this issue. @jbenet agree? |
Yep it should. Cause I think levigo/leveldb is re entrant.— On Sun, Oct 5, 2014 at 8:04 PM, Jeromy Johnson notifications@github.com
|
ribasushi
pushed a commit
that referenced
this issue
Jul 4, 2021
Support in-memory pipes to read from log
ariescodescream
pushed a commit
to ariescodescream/go-ipfs
that referenced
this issue
Oct 23, 2021
gx: update go-ws-transport
hacdias
pushed a commit
that referenced
this issue
Nov 29, 2023
This commit was moved from ipfs/interface-go-ipfs-core@de3410b This commit was moved from ipfs/boxo@ea6ac8c
hacdias
pushed a commit
that referenced
this issue
Nov 29, 2023
This commit was moved from ipfs/interface-go-ipfs-core@de3410b This commit was moved from ipfs/boxo@ea6ac8c
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some datastores are not thread-safe. Eg.
Datastore
implementations backed by the Gomap
.Proposal: Introduce
datastore.go
's newThreadsafeDatastore
interface.Original: #85 (comment)
The text was updated successfully, but these errors were encountered: