fix(keystore): use new batch after commit#1154
Merged
guillaumemichel merged 1 commit intomasterfrom Sep 23, 2025
Merged
Conversation
gammazero
approved these changes
Sep 23, 2025
|
I have same error on arm64 Linux [Release 0.38]. What can I do? Until the next release, can't use the pebble database? It's very crappy if that's the case. |
Collaborator
Author
|
@gyurmogyuri This PR fixes the panic in the The fix for kubo is ipfs/kubo#11011 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, we recycled the old datastore batch after it was committed, resulting in
panic: pebble: batch already committing.We now create a new batch after committing the previous one.