openedx / openedx/xqueue-watcher
When grader error occurs, stderr should be logged
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 18
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
at https://github.com/edx/xqueue-watcher/blob/fd79253eb524c9e8d8d4d769107ae9c9dd85e113/xqueue_watcher/jailedgrader.py#L146 only stdout gets logged, but it would be very helpful to also see stderr since it often includes output like the exception trace or that the sudo user for the codejail isn't configured correctly.
I plan on writing the code to add it, I just wanted to note it here while I remember.
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
Start at xqueue_watcher/jailedgrader.py around line 146, where stdout is logged during a grader error. Trace the surrounding error-handling path and add stderr to the logged output; done means exception traces and codejail configuration errors are visible in the logs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100