Do not skip root tree when searching for trees#5153
Merged
MichaelEischer merged 4 commits intorestic:masterfrom Jan 13, 2025
Merged
Do not skip root tree when searching for trees#5153MichaelEischer merged 4 commits intorestic:masterfrom
MichaelEischer merged 4 commits intorestic:masterfrom
Conversation
b5e3b5f to
d050c28
Compare
added 2 commits
November 28, 2024 10:28
This fixes an issue where restic cannot find the tree when trying to find the tree id of a snapshot.
d050c28 to
afdeece
Compare
Member
|
The linter is still unhappy:
|
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
2 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.
This fixes an issue where restic cannot find the tree when trying to find the tree id of a snapshot.
What does this PR change? What problem does it solve?
restic find --tree <id>cannot find the tree referenced byrestic snapshot --jsonsince it skips the root tree when searching.Was the change previously discussed in an issue or on the forum?
Checklist
changelog/unreleased/that describes the changes for our users (see template).