ocurrent / ocurrent/ocurrent-deployer
no history of previous opam.ocaml.org builds
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 24
- Forks
- 18
- Avg merge
- 16m
- Merged PRs (30d)
- 2
Description
While trying to debug why opam.ocaml.org isn't updating, I see this:
But no history of builds. Without the history, it's impossible to tell what's causing the build failure.
@patricoferris noted in another conversation that this may be due to the shape of the ocurrent DAG changing via binds, and so each run of the pipeline is actually a different graph.
In the meanwhile, the deployer is showing orange all the time, and the Hub shows that there hasn't been a push to opam.ocaml.org for 2 days... /cc @tmcgilchrist
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the deployer build-history view and the pipeline DAG behavior around binds described in the issue. Compare the missing history with the Hub's reported lack of pushes to opam.ocaml.org. Done means previous builds remain available so failures and update gaps can be diagnosed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100