-
Notifications
You must be signed in to change notification settings - Fork 1k
Improve logs when recovering from an interrupted installation #4725
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
FranciscoTGouveia
wants to merge
1
commit into
rust-lang:main
Choose a base branch
from
FranciscoTGouveia:logs-interruped-install
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+6
−0
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think in principle this fix is correct, thanks!
However, isn't
.list()doing a FS read every time in this loop? I'd imagine the result of.installation.list()to be perfectly predictable (don't care about ToC/ToU for now), so may I ask what do we have in.components_to_uninstalland.installation.list()here?In other words, could these be two sets of elements of the same format, so that we can make a difference?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, indeed,
.list()implies a FS read, so a reasonable solution may be to enter the loop only if.list()is not empty (i.e., by adding a conditional check before the loop).In this case, as the toolchain was not installed,
.components_to_uninstallwas set to all the 6 components (see here), and.installation.list()was empty.That said, I think a better approach would be to restrict the
components_to_uninstallvector to only include components that actually exist; this comment may be misleading in that regard.This would eliminate the need for the additional check and further simplify the
uninstall_componentfunction.What do you think about this approach?