Skip substitution when the symlink is correct. - #3193
Open
3405691582 wants to merge 1 commit into
Open
3405691582 wants to merge 1 commit into
3405691582 wants to merge 1 commit into
Conversation
In google#3192 we ensure that fetched files are modified during fetch, in order to front-load modifications of fetched resources. Substitution also requires modification of the fetched tree. cvd fetch and cvd start can both trigger substitution -- we require both since we need to operate on fetched and local builds. However, we try to modify the tree during cvd start as well, even when the symlinks are already correct. If we have made the host artefacts read-only after fetching them, the subsequent substitution fails. There's no need to regenerate the symlink; do it once and only once.
Databean
approved these changes
Sep 17, 2026
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
3 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.
In #3192 we ensure that fetched files are modified during fetch, in order to front-load modifications of fetched resources. Substitution also requires modification of the fetched tree. cvd fetch and cvd start can both trigger substitution -- we require both since we need to operate on fetched and local builds.
However, we try to modify the tree during cvd start as well, even when the symlinks are already correct. If we have made the host artefacts read-only after fetching them, the subsequent substitution fails. There's no need to regenerate the symlink; do it once and only once.