nspcc-dev / nspcc-dev/neofs-node
Fix incorrect behavior of reputation client
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
reputationClient is a NeoFS API client implementation which is designed to track success of the operations with remote nodes. After recently introduces changes of Client interface in NeoFS SDK reputationClient no longer submits the results correctly: for example, Client.ObjectGetInit initializes data flow only w/o any transmission. We need some correct and at the same time a convenient way to do it.
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 tracing reputationClient against the recently changed Client interface, focusing on Client.ObjectGetInit and the distinction between initializing a data flow and transmitting results. Identify how operation outcomes are currently submitted and define a consistent, convenient approach for all affected operations. Done means reputationClient correctly submits results to remote nodes, including after ObjectGetInit.
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
- 35/100