fix: --save-defaults elevates like a normal run - #10
Merged
Conversation
scan/connect/all called require_root_for after the --save-defaults early return, so a save-only invocation never elevated and failed writing settings.json with EACCES when the config dir needs sudo (e.g. left over from a previous elevated run). Move require_root_for ahead of the save-defaults block so it elevates first.
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
1 participant
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.
scan/connect/all returned before
require_root_forwhen--save-defaultswas set, so a save-only run never elevated and failed writingsettings.jsonwithEACCESwhen the config dir needs sudo. Elevate before the save-defaults early return (same as a normal run), then persist and exit.