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
Binary cache substituter does not handle server errors gracefully #396
Comments
Still happens for |
Temporary workaround suggestion for those having issues after doing
|
Ran into this today with an internal Hydra instance. I couldn't figure out how to get around it, so I just temporarily disabled the cache. |
Interestingly |
@domenkozar: I ran into the same issue, see #807. |
Yes, it was importing nixpkgs from nix store |
This works correctly in 2.0. |
It sure does! |
@edolstra, would it be considered a bug in Nix 2.0 if a |
Instantiation or build failure? I guess it could only happen at instantiation time if you're importing from a derivation. At build time, it would be a bug if the build failed on a 410 without |
@edolstra, we have managed to reproduce the build failure -- the relevant details captured in https://gist.github.com/cleverca22/2038f9abd1f9778e66b63fdf02d67054 Michael clarified that Nix is |
Yeah temporary workaround would be to patch Hydra to return 404 instead of 410. |
Replacing 410 with 404 (as per https://github.com/input-output-hk/iohk-ops/pull/348/files) didn't help:
|
Ah that's a missing nar, not narinfo. I think hydra should return 404 for narinfo if nar is missing. (although Nix should handle such case gracefully) |
@edolstra, do you find it appropriate to have a corresponding |
E.g. if a NAR has disappeared from the server (as often happens with Hydra), it says:
The bzip2 error is because we're piping curl directly into bzip2.
The error message should be improved. Also, for a 410 Gone error, we should just proceed as if we never got a .narinfo for this path from the server.
The text was updated successfully, but these errors were encountered: