biocore / biocore/microsetta-private-api
When BadRequest is raised, we don't observe traceback in our log files
Open
- Dominant language
- Python
- Stars
- 6
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
...this is not great as if the BadRequest is thrown by survey_answers_repo, it's unclear what specific line is throwing it
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing where BadRequest is raised or handled around survey_answers_repo and inspect how exceptions are written to log files. Done means the relevant traceback identifies the specific line that raised BadRequest; the issue does not name a file or test to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100