man-group / man-group/notebooker
Bug: A very long-running check (>1h) will be marked as timed out
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 939
- Forks
- 95
- Avg merge
- 9d 1h
- Merged PRs (30d)
- 1
Description
However, when the check completes it will save properly. In the time range from T0+1h to report completion, it appears that the report has completely failed, but it is working fine.
We need to potentially send a heartbeat to ensure that it is not improperly marked as having failed/timed out when it is actually running in the background.
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
The issue names no files, tests, or entry points. Start by locating the check timeout handling and the background completion path, then verify that a run longer than one hour remains non-failed until completion and still saves correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook, python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100