Add timeouts to DeepSeek requests
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
Research direction
Start at the DeepSeek client call in the FastAPI request path and trace how upstream exceptions become API responses. Add a focused timeout-failure test and verify that finite, configurable request timeouts produce a controlled API error.
Written by the indexing model from the issue text.
Description
Problem
The DeepSeek client call has no explicit timeout, so an upstream network problem can hold an API request indefinitely.
Acceptance criteria
- Configure a finite timeout for model requests.
- Make the value configurable if appropriate.
- Add a test that confirms timeout failures become a controlled API error.
- Dominant language
- Python
- Stars
- 3
- Forks
- 10
- Avg merge
- 14h 44m
- Merged PRs (30d)
- 9
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.
More from ashrafee-dev/scamshield-api
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
All issues in ashrafee-dev/scamshield-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100