-
Notifications
You must be signed in to change notification settings - Fork 542
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
Cache seems totally broken -- glide up
only works after glide cc
#658
Comments
@myleshorton Can you provide details about your setup (glide and os versions) and any example output? Did |
Hey sorry for the delay @mattfarina. Here's more info:
Running Sierra:
That's the odd thing -- glide up appears to run successfully every time with no errors. I'll try to get more verbose output next time I see it. |
Yup -- saw this again just now. Master for getlantern/interceptor just changed. getlantern/flashlight (private) depends on it (so maybe it's something with private repos?), and running
|
Just did this from another repo that's not private. Here's the diff after Very frustrating.
|
Sure enough |
Experiencing the same here, can confirm that glide does not pick up any new versions of the packages when they are in cache, after the cache is cleaned up the new version is picked up |
Any update on this? We see it frequently here and doing |
the issue here is most likely what we're discussing in #592. the glide authors have been a bit taken up with other things of late, but this particular fix should not, i don't think, be heinous. closing issue in favor of that one. |
Without call
glide cc
firstglide up
just doesn't find updates from dependencies. Crazy.The text was updated successfully, but these errors were encountered: