nspcc-dev / nspcc-dev/neofs-node
cli: Placement bulding error looks unclear
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
I formulated an a priori unenforceable network storage policy by making the number of replicas greater than the current number of nodes. I called neofs-cli container nodes command to check. Origin error was
not enough nodes to SELECT from: ''
While not enough nodes looks clear to me, selection part looks not, what empty string do we have here? I propose to clarify the case. Note that the error message is produces by NeoFS SDK Go lib.
P.S. the case can be spread to other CLI commands which build container placement.
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 with the neofs-cli container nodes command and trace the container-placement commands that produce the NeoFS SDK Go error. Check how the empty selection value reaches the message and whether related CLI commands share the same path. Done means the insufficient-node case reports a clear, useful selection context across the affected commands.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100