ashrafee-dev / ashrafee-dev/scamshield-api
Handle Redis connection failures gracefully
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Python
- Stars
- 3
- Forks
- 10
- Avg merge
- 14h 44m
- Merged PRs (30d)
- 9
Description
Goal
Return a controlled service response when Redis is unavailable instead of exposing an unhandled connection exception.
Acceptance criteria
- Catch the relevant Redis connection error at the API boundary or rate-limit service.
- Choose and document an appropriate HTTP/WebSocket error behavior.
- Add a test that simulates Redis being unavailable.
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 locating the FastAPI API boundary and rate-limit service code that accesses Redis, then identify the connection exception currently exposed to callers. Decide and document the appropriate HTTP or WebSocket failure behavior, add a test that simulates Redis being unavailable, and run the relevant service tests to verify a controlled response.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python, redis
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100