-
-
Notifications
You must be signed in to change notification settings - Fork 296
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
Don’t prefetch greedy outdated casks #1309
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This pull request changes bundle's behavior to only check whether one cask is outdated at a time (for greedy updates).
Can you explain why this is better?
What network requests does this avoid?
For all of the following casks…
(a few dozen nightlies from …the entire current file has to be downloaded every time to check whether the contents that would be installed are equivalent. Thanks for the notes, I don't deal with ruby often 😅 |
Yeh, this is expected when using Does this mean that |
Well, it won’t download a cask without the |
If you don't use So is it now that |
Yup! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks so much for your first contribution! Without people like you submitting PRs we couldn't run this project. You rock, @jneubrand!
In some instances, calling
.outdated?(greedy: true)
causes additional network requests. (casks usingversion :latest
andsha256 :no_check
seem to trigger this)Currently, this is done for all installed packages every time
brew bundle
wants to update any cask greedily.This pull request changes
bundle
's behavior to only check whether one cask is outdated at a time (for greedy updates).