nspcc-dev / nspcc-dev/neofs-node
Expend control status for every operation.
Open
Nobody has claimed this yet.
enhancement
I3
S4
U3
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Is your feature request related to a problem? Please describe.
As mentioned in https://github.com/nspcc-dev/neofs-node/issues/2585#issuecomment-1725809368 there is a possibility to make the process more detailed by adding new control statuses.
Describe the solution you'd like
extend HealthStatus enums
Describe alternatives you've considered
do not change
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
Start by reading the discussion linked from issue 2585, especially the referenced comment, to understand which additional control statuses are expected for each operation. Then locate the Go definition of the HealthStatus enums and the code that reports them. Done means the enums and their operation status handling cover the agreed cases, with relevant tests updated or added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100