Track pending pings to retry later
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 32
- Forks
- 0
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Save the scheduled and failed pings into an item which gets written to the cache after each ping has completed (after either removing or marking as failed, accordingly). OR these items into the scheduled list when the target list is computed.
This will help with the case that Pushl gets interrupted partway through (or the receiving endpoint happens to be down/erroring at the time), so pings aren’t lost forever.
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 tracing how pings are scheduled, completed, removed or marked failed, and how the cache is written. Define how pending items are persisted after each ping and merged into the next computed scheduled list. Done means interrupted or failed pings remain available for a later retry rather than being lost.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100