Puneeth Chaganti

> I am in favour of already raising this to 4.08 The plan for deprecation is [here](https://github.com/ocaml/opam-repository/issues/23789#issuecomment-2220562013) and a draft policy for similar updates in future is [here](https://hackmd.io/@shon/Hy5BqVS_C).

Looks like [this](https://github.com/ocaml/opam/commit/e66648f07b950e5ba144a477432f437bfd8059ec) is the offending commit.

The logs for the set-status job look like this: ``` 2023-04-25 17:53.03: New job: Set ocaml/opam refs/heads/master e66648f0/ocaml-benchmarks to {"state":"pending","target_url":"https://autumn.ocamllabs.io/ocaml/opam"} 2023-04-25 17:53.03: Waiting for resource in pool github 2023-04-25 17:53.07:...

Okay, thanks for the additional information.

Hey @liweijian It looks like a transient network issue on your end, or an issue accessing docker hub for some reason. You could try building again, may be using a...

We happened to restart the current-bench pipeline, after deploying some changes. The error message is unclear and could be confusing, but a [new build](https://autumn.ocamllabs.io/ocaml/merlin/pull/1640/base/master?worker=autumn&image=bench.Dockerfile) should automatically start for that commit...

On PRs, cancelling the previous run may still be a good idea, but on `master` we still want to benchmark for those commits, I think. Leaving the status as `pending`...

> The frontend and database communicate using graphql. It could be done better when the above are done. If we port the frontend/UI to Dream + HTML, do we still...

> The good news is that we don't actually that much javascript on the frontend! We could just have a standard webserver written in OCaml and push HTML to the...

#436 is also somewhat related to this.