MatterMiners / MatterMiners/lapis
Logging of failed job results in exception in logging
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
When a job fails the reason will be logged. However, at this state the drone is already set to None resulting in an error as the relevant information cannot be accessed anymore.
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
Trace the failed-job handling and its logging path to find where the drone is set to None before the failure reason is accessed. Reproduce a failed job and inspect the resulting logging exception. Done means the failure reason is logged without raising a second exception.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100