Switch dqlite to 1.16.5 and go-dqlite to 1.21.0 (5.0-candidate) #627
Conversation
This file contains 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
Signed-off-by: Thomas Parrott <[email protected]>
And revert commit that switches LXD to go-dqlite v2. This is related to a suspected crash caused by dqlite v1.17.1 or go-dqlite v2.0.0 and beyond. Whilst its being investigated we will stick with the previously known good combination from LXD v5.21.2. Signed-off-by: Thomas Parrott <[email protected]>
tomponline
force-pushed
the
5.0-candidate
branch
from
85e764b to
8c71034
Compare
mihalicyn
approved these changes
Nov 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
And revert commit that switches LXD to go-dqlite v2.
This is related to a suspected crash caused by dqlite v1.17.1 or go-dqlite v2.0.0 and beyond.
Whilst its being investigated we will stick with the previously known good combination from LXD v5.21.2.