getLog() should not return an error if the log file is not available
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 184
- Forks
- 53
- Avg merge
- 7d 2h
- Merged PRs (30d)
- 1
Description
This can happen if the HPC scheduler kills the jobs before logs can be written, or if the HPC scheduler does not report the job as in the system when in fact it is running. getLog() should return NULL if no log is available and perhaps show a warning, not an error which stops execution.
https://github.com/mllg/batchtools/blob/ed75f6951a1603b2899b24ffb18b045190e8f863/R/Logs.R#L119
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
Open R/Logs.R at line 119 and inspect getLog() handling when the log file is unavailable. Reproduce or trace the missing-log path, then verify that it returns NULL and handles the condition without stopping execution; no test file is mentioned in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- hpc
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100