Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Slow, unnecessary version check updates on unrelated command #1170

Open
LilithHafner opened this issue Feb 11, 2025 · 4 comments · May be fixed by #1189
Open

Slow, unnecessary version check updates on unrelated command #1170

LilithHafner opened this issue Feb 11, 2025 · 4 comments · May be fixed by #1189

Comments

@LilithHafner
Copy link
Member

When installing channel 1.8, I don't want to check for updates to other channels. Especially not if that slows down the instillation of the channel I'm asking for.

In this case, the "Checking for new version" steps took longer than the "Installing" step.

$ julia +1.8
ERROR: `1.8` is not installed. Please run `juliaup add 1.8` to install channel or version.
$ juliaup add 1.8
Checking for new Julia versions
Checking for new version on channel 'pr55152' is taking a while... This can be slow due to server caching
Checking for new version on channel 'nightly' is taking a while... This can be slow due to server caching
Checking for new version on channel 'pr56882' is taking a while... This can be slow due to server caching
Checking for new version on channel 'pr56707' is taking a while... This can be slow due to server caching
Installing Julia 1.8.5+0.aarch64.linux.gnu
@LilithHafner
Copy link
Member Author

Moments later, I tried to add version 1.7 and all these same channels were re-checked. This is impactful in the case of bisecting based on Julia version.

@KristofferC
Copy link
Member

This is annoying because I get an error when the nightly check happens now which means I cannot add a new normal julia version at all.

@StefanKarpinski
Copy link
Member

Would be fine if the update checks were done in the background or not at all.

@davidanthoff
Copy link
Collaborator

We should keep checking for a versions db update (and if there is one download it) to make sure the add command actually operates on the latest version info, but I agree, we should not check for updates for any of the "direct download" channels, that has no purpose when an add is executed and is the part that is slow.

@christiangnrd christiangnrd linked a pull request Mar 28, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Only check for direct download versions when necessary christiangnrd/juliaup
4 participants
@StefanKarpinski @davidanthoff @KristofferC @LilithHafner