marigold-dev / marigold-dev/deku
Hard-forks on a fast shutdowns
Open
Nobody has claimed this yet.
- Dominant language
- OCaml
- Stars
- 82
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
Shutting down the chain quickly can leave the chain in a bad state during development, making development cumbersome (especially with Docker).
We should implement more graceful shutdown.
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
No files, tests, or entry points are named. Reproduce a fast shutdown during development, then inspect the shutdown path and Docker setup to identify where state is left inconsistent. Done means a quick shutdown is graceful and does not leave the chain in a bad state on restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ocaml
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100