-
-
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
Badger still crashing on shutdown after latest fixes #6986
Labels
kind/bug
A bug in existing code (including security flaws)
Milestone
Comments
Is #7015 the fix-approach for this? Still happening on master (when adding offline). |
Damn. I thought I fixed it. |
Stebalien
added a commit
to ipfs/go-ds-badger
that referenced
this issue
Apr 8, 2020
fixes part of ipfs/kubo#6986 (the other part is that we should be shutting down in the right order)
Stebalien
added a commit
that referenced
this issue
Apr 8, 2020
Stebalien
added a commit
to ipfs/go-ds-badger2
that referenced
this issue
Apr 16, 2020
fixes part of ipfs/kubo#6986 (the other part is that we should be shutting down in the right order)
ralendor
pushed a commit
to ralendor/go-ipfs
that referenced
this issue
Jun 6, 2020
ralendor
pushed a commit
to ralendor/go-ipfs
that referenced
this issue
Jun 6, 2020
ralendor
pushed a commit
to ralendor/go-ipfs
that referenced
this issue
Jun 8, 2020
ralendor
pushed a commit
to ralendor/go-ipfs
that referenced
this issue
Jun 8, 2020
ralendor
pushed a commit
to ralendor/go-ipfs
that referenced
this issue
Jun 8, 2020
ralendor
pushed a commit
to ralendor/go-ipfs
that referenced
this issue
Jun 8, 2020
hannahhoward
pushed a commit
to filecoin-project/kubo-api-client
that referenced
this issue
Jun 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version information:
Local build off 6ae79efc2f86
Description:
Badger crashes on shutdown despite the latest merged fixes ( this issues is separate from #6985 ).
@Stebalien I actually can not find a badger-related merge in master's history...nevermind, apparently this was fixed ages ago, which is why I couldn't find it.The text was updated successfully, but these errors were encountered: