nspcc-dev / nspcc-dev/neofs-node
Meta signature collection in relay scenario
Open
Nobody has claimed this yet.
bug
I4
neofs-storage
S3
U3
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Expected Behavior
When a node is just a relayer (it doesn't store an object) it should still collect/push meta signatures since it's the one responsible for replication.
Current Behavior
Only "local node" handles signatures.
Possible Solution
Fix it.
Context
#2878, #3029.
Your Environment
- Version used: master
- Server setup and configuration:
- Operating System and version (
uname -a):
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
The issue names no file, test, or entry point. Review issues #2878 and #3029 first, then trace meta-signature handling for the relay scenario. Done means a relaying node that does not store the object collects and pushes the required meta signatures, with coverage for that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100