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
Panic in Leveldb #6880
Labels
exp/expert
Having worked on the specific codebase is important
help wanted
Seeking public contribution on this issue
kind/bug
A bug in existing code (including security flaws)
panic
status/ready
Ready to be worked
Comments
Hm. Looks like an issue with closing while iterating. I guess we'll need to port the fix from go-ds-badger and take a RWLock when accessing/closing. |
Also, we should fix how we manage the provider queue such that we wait for it to stop before trying to close the datastore. |
Stebalien
added
status/ready
Ready to be worked
exp/expert
Having worked on the specific codebase is important
help wanted
Seeking public contribution on this issue
labels
Feb 7, 2020
willscott
added a commit
to ipfs/go-ds-leveldb
that referenced
this issue
Feb 20, 2020
Add a `sync.RWMutex` protecting the Close operation. Follows the same pattern as in go-ds-badger. Address #29 / ipfs/kubo#6880
willscott
added a commit
to ipfs/go-ds-leveldb
that referenced
this issue
Feb 25, 2020
Add a `sync.RWMutex` protecting the Close operation. Follows the same pattern as in go-ds-badger. Address #29 / ipfs/kubo#6880
willscott
added a commit
to ipfs/go-ds-leveldb
that referenced
this issue
Feb 25, 2020
Add a `sync.RWMutex` protecting the Close operation. Follows the same pattern as in go-ds-badger. Address #29 / ipfs/kubo#6880
Fixed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
exp/expert
Having worked on the specific codebase is important
help wanted
Seeking public contribution on this issue
kind/bug
A bug in existing code (including security flaws)
panic
status/ready
Ready to be worked
The text was updated successfully, but these errors were encountered: