-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
Global cache issues #211
Comments
oh, i just try to find why my shard not updated, |
It seems like if you are using a branch for the version it should always have a cache miss. |
but 0.29 there is, i just push it.
|
Sigh. Can someone reproduce and run shards commands with I won't be able to look at this anytime soon. |
It's probably not the global cache, but not mirroring the Git repository anymore. A simple |
If you type git commands in the cached git folder, you probably won't see the new tags, even after a |
after pushing v0.2
after
|
i just test it, it works if replace |
Creating bare Git repositories doesn't configure the local repository to fetch remote refs, such as branches and tags, which totally broke the update command. This patch reverts back to mirroring Git repositories, and verifies whether a cloned repository is valid, or not before fetching new refs. fixes #211
Creating bare Git repositories doesn't configure the local repository to fetch remote refs, such as branches and tags, which totally broke the update command. This patch reverts back to mirroring Git repositories, and verifies whether a cloned repository is valid, or not before fetching new refs. fixes #211
Creating bare Git repositories doesn't configure the local repository to fetch remote refs, such as branches and tags, which totally broke the update command. This patch reverts back to mirroring Git repositories, and verifies whether a cloned repository is valid, or not before fetching new refs. fixes crystal-lang#211
Creating bare Git repositories doesn't configure the local repository to fetch remote refs, such as branches and tags, which totally broke the update command. This patch reverts back to mirroring Git repositories, and verifies whether a cloned repository is valid, or not before fetching new refs. fixes crystal-lang#211
I just updated to 0.25 of Crystal which uses shards 0.8 with the new global cache.
The shard cache failed to update under these circumstances:
lucky_cli
) inshard.yml
usingversion
branch: master
shards update
lucky_cli
shards update
branch: master
instead of updatingTemporary fix
rm -rf ~/.cache/shards
and re-run `shards update.Possible fix
shards update
always update cache if usingbranch
ortag
?The text was updated successfully, but these errors were encountered: