-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
nix-build --falback does not allow you to build local packages when nixos.org is down #93
Comments
We were 1) using CURLOPT_TIMEOUT instead of CURLOPT_CONNECTTIMEOUT; 2) not passing it to the curl child process. Issue #93.
You can now set a connection timeout via $NIX_CONNECT_TIMEOUT or I can't reproduce the problem with --fallback though, |
I have exactly the same problem on my system: cache.nixos.org is down, I tried every options (
It seems that the options are taken into account. Some details:
|
For posterity: it seems this should be The |
chore(deps): bump sphinx from 3.2.0 to 3.2.1
TL;DR: nixos.org is a single point of failure.
Just started using nix yesterday, trying to write my own packages (on Mac OSX).
I cloned nixpkgs and started hacking.
This morning nixos.org is down. That's ok, even amazon goes offline every once in a while. However I cannot seem to get nix-build to ignore nixos.org.
Tried:
After waiting literally for:
The build does not continue with the error:
Isn't the whole point of --fallback not to require a binary cache?
Some more output follows the error:
Then I tried editing
and changed the while loop in
processRequests
to:to make the script exit immediately.
With this change
finished alot faster, however again trying to download
gnumake
from a binary cache, giving up after 2 minutes and 32 seconds.What does --fallback do again?
Then I tried (getting desperate here)
For some reason when I change the binary-caches option, nix-build wants to build a whole lot more packages, like curl. I'm guessing it ignores every dependency already existing in the
/nix/store/
?!The build proceeds extremely slow and prints errors like these:
I hope this is fixed quickly, I would not want to use disnix in production and not be able to fix my servers when nixos.org is down! That's a serious single point of failure!
And even if --fallback did work properly, the HTTP connect timeouts are way too high.
The text was updated successfully, but these errors were encountered: