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

caml.inria.fr is not accessible anymore #13237

Closed
kit-ty-kate opened this issue Jun 14, 2024 · 12 comments
Closed

caml.inria.fr is not accessible anymore #13237

kit-ty-kate opened this issue Jun 14, 2024 · 12 comments

Comments

@kit-ty-kate
Copy link
Member

I was trying to download the archive for OCaml 4.14.2 and got hit by a "Couldn't connect to server".
Going to the website in HTTPS indeed results in a timeout, and trying the HTTP version nets me this page instead:
scrn-2024-06-14-13-47-58

@shindere
Copy link
Contributor

shindere commented Jun 17, 2024 via email

@xavierleroy
Copy link
Contributor

Yep, the servers are moving, and as it says on the error page, "the websites are scheduled to go back online on June 19 or 20, 2024". I was hoping no one relies on caml.inria.fr any longer...

@kit-ty-kate
Copy link
Member Author

I was hoping no one relies on caml.inria.fr any longer...

if this is the case, i think it would be nice for the archives created by hand for each releases to be added to the GitHub release page (cc @Octachron), this way we have a set of immutable archives. I believe this is the only reason people still use caml.inria.fr

PS: sorry @shindere i should've thought of adding an alt-text for the image, i'll try to remember for next time

@Octachron
Copy link
Member

It is a good idea to add the archive to the GitHub release page anyway.

@shindere
Copy link
Contributor

shindere commented Jun 17, 2024 via email

@avsm
Copy link
Member

avsm commented Jun 17, 2024

It looks like some package managers still have the caml.inria.fr server baked in; e.g. NixOS' nixpkgs:
https://github.com/NixOS/nixpkgs/blob/master/pkgs/development/compilers/ocaml/generic.nix#L27

So uploading the caml.inria.fr archives with the same SHA256 hash to the corresponding GitHub release would be indeed a very useful way to make the fix for Nix is a one line change instead of updating all the checksums as well.

@mtelvers
Copy link

caml.inra.fr is also embedded into the opam build process for 2.0 and 2.1, preventing us from building new Docker base images for the CI system. ocurrent/docker-base-images#283

As the opam files for the compiler in the opam-repository have recently been touched via various PRs, the CI system is rebuilding the compiler even though it already exists in the current switch. This is slowing the CI system and causing the workers to repeatedly hit the websites, which host the dependencies needed to compiler OCaml. This is resulting in curl failures due to rate limits on those sites. See ocaml/infrastructure#128.

Opam 2.0 needs a lot of effort to get it to pass CI, but 2.1 could easily be patched to remove the dependency on caml.inria.fr. OCaml-CI uses opam 2.1, Opam-repo-ci uses opam-dev. Does anyone still use opam 2.0?

@mtelvers
Copy link

Further to my last comment, the patch to opam is more straightforward than I thought. It is the bootstrap compiler that is failing, so one patch on master will resolve the issue. See ocaml/opam#6032.

@shonfeder
Copy link

Would it be possible for inria to redirect requests for these archives (and for opam) to the source on github for the duration of their outage? If so, is that lift light enough that we could expedite to address the immediate impact of these disruptions?

@shindere
Copy link
Contributor

shindere commented Jun 21, 2024 via email

@gasche
Copy link
Member

gasche commented Jun 21, 2024

Note: caml.inria.fr is back online (probably has been since yesterday).

@shindere
Copy link
Contributor

shindere commented Jun 21, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants