Global infinite retries cause a lot of problems
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 307
- Avg merge
- 17h 44m
- Merged PRs (30d)
- 256
Description
Your Account Type
- Wire Personal Account
- Wire Pro Account
- Wire Enterprise Account
- Wire Red Account
What steps will reproduce the problem?
Clicking on a contact in the Contacts bar, I want to open a new conversation, but due to network problems, the request fails, and then I click multiple times, which results in multiple retry requests. When the network is restored, multiple conversation appear.
What is the expected behaviour?
Click on a contact multiple times, even if a network problem causes the request to result in, when the network is restored, only one conversation will appear
In api-client, axios-retry is used, so all requests are retried infinite. In fact, it's not just the problem I reported above, but also in other behaviors. This is caused by infinite retries. This issue does not occur in Android/IOS versions.
I don't think global infinite retries are a good design, they should be done only when they are really needed, like sending a message.
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
Start in the api-client configuration where axios-retry is enabled, and reproduce a failed contact request followed by multiple clicks during a network outage. Determine the retry behavior and verify that restoring the network produces only one conversation, with retries limited to explicitly needed operations rather than applied globally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, frontend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100