Add tests to ensure we don't leak detailed errors
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 6
- Forks
- 2
- Avg merge
- 9h 7m
- Merged PRs (30d)
- 2
Description
We don't have coverage for these cases (to ensure we don't leak any other output), but that can be a follow up.
Originally posted by @StanFromIreland in #61
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 reading the referenced discussion in pull request #61 to identify the error cases and the existing test entry points. Add coverage for those cases, ensuring no detailed or unintended output is exposed, and run the relevant test suite to confirm the checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100