oasisprotocol / oasisprotocol/oasis-core
Crashes on Out of Space
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 369
- Forks
- 151
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Out of a total of nine nodes I run (four on docker, five native), only Oasis and an old bitcoin copy-paste-fork crashed and ceased running due to a temporary out of space condition that was then resolved hours later.
Note that this was an edge case with Github being down yesterday and bug in an autoupdate script recursively copying my home directory into a single directory infinitely. Still, Oasis needs to be made much more robust if other nodes can handle it.
Contributor guide
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. Start by locating Oasis node handling for disk-full conditions and reproduce a temporary out-of-space state; done means the node remains running or recovers cleanly after space is restored, with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100