nspcc-dev / nspcc-dev/neofs-node
Split verification and storage code for incoming objects
Open
Nobody has claimed this yet.
good first issue
I4
neofs-storage
S4
U4
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Originally posted in https://github.com/nspcc-dev/neofs-node/pull/2674#discussion_r1540004148
it's proposed to split VerifyObject and StoreObject functionality, both independent and reusable
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 VerifyObject and StoreObject functionality described in the issue and review the original discussion in pull request #2674. Determine where the incoming-object verification and storage paths are implemented, then confirm that each can be used independently and reused without coupling them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100