Fix reinstall loop when tool has both binaryPath and desiredBinaryName#74
Merged
albertodebortoli merged 2 commits intomainfrom Apr 19, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Pull Request Title
Fix reinstall loop when tool has both
binaryPathanddesiredBinaryNameDescription
isToolInstalledcheckedbinaryPathbeforedesiredBinaryName. After first install, the archive binary is renamed todesiredBinaryNameon disk, sobinaryPathno longer exists. On subsequent runsisToolInstalledreturnedfalse, triggered a full re-download, re-extracted the archive, then failed with "item with the same name already exists" when trying to rename again.reinstallnow also checksdesiredBinaryNamebeforebinaryPathwhen resolving the on-disk binary, making the intent explicit and consistent with the install path.Type of Change
How Has This Been Tested?
Two new regression tests:
InstallerTests/test_reinstall_withDesiredBinaryName_doesNotRedownload— installs a tool twice and asserts the downloader is called exactly once (second run takes the reinstall path, not re-download).ToolInstallerTests/test_reinstall_withDesiredBinaryName_usesDesiredNameForSymlink— callsreinstallon a tool whose binary is stored underdesiredBinaryNameand verifies the symlink is created correctly.Checklist
CI Considerations
Breaking Changes?
Additional Notes
Reproducer (Lucafile entry that triggered the bug):