MixinNetwork / MixinNetwork/bot-api-nodejs-client
PIN incorrect error when slow network
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 12
- Avg merge
- 1d 51m
- Merged PRs (30d)
- 5
Description
When a request includes encrypted pin timeout，if client doesn't receive a response, it would send the same request again and the first request would take effect, which leads to the Pin incorrect error.
Maybe do not retry when request involves encrypted pin and network timeout
Contributor guide
No contributing guide indexed for this repository
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
Trace the request retry path for calls involving an encrypted PIN, focusing on the timeout case where the client receives no response. Reproduce the duplicate-request scenario and verify that encrypted-PIN requests are not retried after a network timeout and no longer produce a PIN incorrect error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- api, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100