Always clean up temporary audio files
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 70/100
Research direction
Locate the /audio and /ws entry points and trace where temporary audio files are created and processed. Add a focused failure-path test or testable helper, then verify that files are removed after both successful and failed transcription or assessment.
Written by the indexing model from the issue text.
Description
Problem
Temporary files created by /audio and /ws may remain on disk if transcription or assessment raises an exception.
Acceptance criteria
- Use
try/finallyor an equivalent cleanup mechanism. - Ensure cleanup occurs for successful and failed processing.
- Add a focused test or testable helper for the failure path.
- 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
-
documentation help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
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