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.

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

Fallback to other version adhering to user-provided spec, if the first can't be fetched #56

Open
jakub-g opened this issue Jun 19, 2014 · 2 comments

Comments

@jakub-g
Copy link
Collaborator

jakub-g commented Jun 19, 2014

$ node --version
v0.10.29

$ nodist 0.8
Couldn't fetch 0.8.27: HTTP 404.
Sorry.

$ node --version
v0.10.29

404 error from the server shouldn't block me from switching the node version. It should fall back to the latest 0.8.x available.

I can work around this using nodist 0.8.26 (which I already have installed before) but nonetheless this, however rare it is, probably should be fixed.

@marcelklehr
Copy link
Member

Nodist falls back to the local version list if fetching the list of available versions fails.

The rationale for not retrying probably was, that it's unlikely that fetching the list succeeds and fetching an executable from that list afterwards suddenly doesn't.

However, the outcome in your case is certainly not desirable. I'll see what i can do.

@marcelklehr
Copy link
Member

Ok, so the nodejs.org server is actually missing the builds for v0.8.27 (see nodejs/node-v0.x-archive#7805)....

@marcelklehr marcelklehr added this to the 0.6 milestone Jul 13, 2015
@marcelklehr marcelklehr removed this from the 0.6 milestone Dec 8, 2015
@marcelklehr marcelklehr changed the title Impossible to switch node version in case of 404 from update server Fallback to other version adhering to user-provided spec, if the first can't be fetched Dec 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants