nspcc-dev / nspcc-dev/neofs-node
Report `GetECPart` shard errors
Open
Nobody has claimed this yet.
enhancement
I4
neofs-storage
S3
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.
StorageEngine.Gettracks handles shard errors specifically- after to #3534,
StorageEngine.GetECPartdoes not
Describe the solution you'd like
assess the need for error accounting in GetECPart. If necessary, implement and test
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 comparing StorageEngine.GetECPart with the shard-error handling in pkg/local_object_storage/engine/get.go, especially the linked section around line 93. Determine whether GetECPart needs equivalent error accounting, then add or update tests to demonstrate the required behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100