Option to cap logs
Open
Nobody has claimed this yet.
Discussion
Enhancement
- Dominant language
- Python
- Stars
- 176
- Forks
- 74
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 21
Description
It would be interesting to have an option, as a competition organizer, to limit the size of the logs the participants can return.
In many cases, we want to avoid that the participants print out private information (sensitive data, ground truth, etc.)
Contributor guide
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
No file, test, or entry point is named. Start by tracing how participant-returned logs are received, stored, and displayed, then identify where an organizer-configured size limit could apply. Done should include a documented limit and verification that oversized logs are capped without exposing sensitive data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100