You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When rebuilding a package, zarf will attempt to use repositories that already exist in the ~/.zarf-cache/repos directory. When testing the fix for another (relatively similar issue) I realized that rebuilding the same package multiple times (3+ times) will result in a failure because the HEAD of the repository in the cache directory ends up picking up changes from online-upstream somehow.
Steps to Replicate
Running from the root of the Zarf repo
# make sure the cache is clear
zarf tools clear-cache
# Build all the things!
zarf package create examples/git-data/ --confirm # This will result with the git repositories being added to the cache
zarf package create examples/git-data/ --confirm # This will result with the cached repositories having unstaged changes
zarf package create examples/git-data/ --confirm # This will result in a creation failure
The text was updated successfully, but these errors were encountered:
## Description
Fixes a bug introduced from MZAL where cache could be messed with do to
GitPath being changed in the git receiver.
## Related Issue
Fixes#1079
## Type of change
- [X] Bug fix (non-breaking change which fixes an issue)
## Description
Fixes a bug introduced from MZAL where cache could be messed with do to
GitPath being changed in the git receiver.
## Related Issue
Fixes#1079
## Type of change
- [X] Bug fix (non-breaking change which fixes an issue)
Related to #1069
When rebuilding a package, zarf will attempt to use repositories that already exist in the
~/.zarf-cache/repos
directory. When testing the fix for another (relatively similar issue) I realized that rebuilding the same package multiple times (3+ times) will result in a failure because the HEAD of the repository in the cache directory ends up picking up changes fromonline-upstream
somehow.Steps to Replicate
The text was updated successfully, but these errors were encountered: