rubyforgood / rubyforgood/skillrx-beacon
Error handling
Open
Nobody has claimed this yet.
cross-app sync
- Dominant language
- HTML
- Stars
- 4
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Robust error handling for low-connectivity scenarios:
- Store failed file IDs in SyncProgress for retry
- Implement SyncRecoveryJob to retry failed files
Contributor guide
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 locating SyncProgress and the proposed SyncRecoveryJob entry points, then trace how failed files are currently handled during low-connectivity scenarios. Done means failed file IDs are stored for retry and a recovery job retries those files successfully.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100