Race condition in IoTScape timeout retries
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1
- Forks
- 2
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
#190 prevents this from causing a bigger issue (at the cost of some usability due to not returning an actual Error), but it seems sometimes the error from retried IoTScape messages was not being forwarded to the client in some cases.
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 by reading issue #190 and tracing the IoTScape timeout-retry handling described here. Reproduce the cases where a retried message's error is not forwarded to the client, then verify that the client receives the expected error without regressing the behavior addressed by #190.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100