[Task]: Retry on Failure for EventHub PublishEvent
Open
Nobody has claimed this yet.
Area/Gateway
Aspect/Performance
Type/Task
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
Area/Gateway (Routing, API deployment in gateway etc.)
Please select the aspect the issue is related to
Aspect/Performance (Latency, optimizations, load issues)
Description
If PublishEvent fails due to database level issue, then it should retry upto three times and then give up
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
Locate the PublishEvent entry point in the gateway and trace how database-level failures are returned. Verify the behavior for up to three attempts, including giving up after the final failure, and add or run the relevant tests if the existing PublishEvent test coverage identifies them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100