Infinite Loop upon not defining maxSubmitRetries
Open
Nobody has claimed this yet.
discussion
- Dominant language
- JavaScript
- Stars
- 6.5k
- Forks
- 456
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 5
Description
On backend.js:27, if maxSubmitRetries isn't given as an option, it goes into infinite loop of retries. And if the error is not resolved, it just causes a dead lock and doesn't spit any errors.
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 at backend.js:27 and reproduce submission with maxSubmitRetries omitted while the underlying error persists. Trace the retry termination and error reporting; done means retries stop without deadlocking and the failure is surfaced to the caller.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100