Repository navigation
fix: keep legacy restore staging scans off GTK - #549
Merged
Merged
Conversation
Linuxuser67
force-pushed
the
fix/main-review-findings
branch
from
October 26, 2026 15:01
86bb833 to
77c7ec2
Compare
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
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.
Summary
Keep potentially blocking destination-directory scans off GTK when restoring legacy queue entries or handling duplicate/missing persisted IDs.
Tests
Review / verification
Reviewed the full PR diff for correctness, clarity, architecture, security, performance, and Rust best practices. This branch includes the latest main, including PR #550. GitHub CI is being run for the current head; local Cargo build/test results are not claimed.