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
{{ message }}
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.
Dep takes a long time to install packages when the cache already has the needed commits. Please correct me if I'm wrong but, it appears dep is going out to the network for updates even when it may not need to.
For the case the Gopkg.lock is present, dep ensure is being run, and nothing is being updated (the lock file isn't changing) dep still goes out to the network.
Is there a way the needed commit could be checked for in the cache and if present skip updating?
The text was updated successfully, but these errors were encountered:
We've been working towards a persistent cache in #431, currently at #1250 and on hold until the next release. Preliminary results show significant speed-up.
Dep takes a long time to install packages when the cache already has the needed commits. Please correct me if I'm wrong but, it appears dep is going out to the network for updates even when it may not need to.
For the case the
Gopkg.lock
is present,dep ensure
is being run, and nothing is being updated (the lock file isn't changing) dep still goes out to the network.Is there a way the needed commit could be checked for in the cache and if present skip updating?
The text was updated successfully, but these errors were encountered: