https://coq.inria.fr/refman/addendum/type-classes.html times out here right now (trying from a German DSL connection)
tried a few machines via SSH and curl
, same result
ping coq.inria.fr
fails both via IPv4 and IPv6
Same here (also Germany)
same, Sweden
Same here (France)...
Damn! Who at Inria do we need to contact?
BTW, as a workaround: you can access the manual at https://coq.github.io/doc/V8.12.0/refman/
I hope it's not another spam submission like the time the website was down for days...
[FWIW, I can still connect to the server.]
Karl Palmskog said:
I hope it's not another spam submission like the time the website was down for days...
That cannot happen anymore since now the website is fully static.
(At that time, the Inria IT staff had overreacted to something posted in our bug tracker.)
not just the manual, but I hear opam’s also down
opam update
fails on coq-released
(The actual data is on https://github.com/coq/opam-coq-archive/tree/master/released, so probably one can adapt the repo URL)
from my understanding, the opam repo is anyway hosted separely from the Coq web server. @Maxime Dénès could perhaps comment on whether there is some alternative URL or hosting options as long as coq.inria.fr is down
No, the two are on the same server.
Actually, I was wrong when I said the server was up. I had forgotten that we had moved to a server hosted outside Inria.
I tested the old Inria server.
But the new (OVH) server is actually unresponsive when trying to log in SSH.
So we need to contact OVH and I think our only point of contact is @Maxime Dénès.
for opam workarounds I created https://coq.zulipchat.com/#narrow/stream/237977-Coq-users/topic/Subdirectories.20of.20git.20repos.20as.20opam.20repos, we have two ways.
Hi guys! Sorry I just noticed this. I'll investigate now. Will report here.
It should be back in a few minutes.
It's back! Apologies for the inconvenience.
Our payment process for OVH is fragile, we hope to improve that soon but so far no solution was suggested to us. We'll debrief this internally, to avoid having this problem again.
Last updated: Jun 08 2023 at 04:01 UTC