learningequality / learningequality/studio
Sync calls error handling
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Summary
Communicate unexpected /api/sync call 500 failure to users. We might also want to try to repeat sync once or twice before that.
Category
ENHANCEMENT
Real-life consequences
Users will know that some data might not be saved properly.
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 tracing the /api/sync entry point and how unexpected 500 failures are currently surfaced to users. Clarify whether the intended scope is communicating the failure, retrying once or twice, or both; done should make failed syncs visible and define the retry behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100