WISH: Clarify the 'Work dir does not exist' error message
Open
Nobody has claimed this yet.
- Dominant language
- R
- Stars
- 184
- Forks
- 53
- Avg merge
- 7d 2h
- Merged PRs (30d)
- 1
Description
With future.batchtools and other wrappers, it become a bit tricky to track down where errors are coming from when running in batch mode. For instance, I got some:
Error : BatchtoolsError in BatchtoolsFuture ('future_lapply-1'): 'Work dir does not exist'
I wasn't sure if that was from the scheduler or batchtools, but it turns out it's from here:
Would you mind updating to something like:
error("Working directory (%s) for the batchtools registry does not exist", jc$work.dir)
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 with R/doJobCollection.R at the linked lines 84-86, where the uninformative work-directory error is raised. Update the message so it identifies the missing working directory and batchtools registry, then verify that the resulting BatchtoolsError reports the directory path clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r
- Domain
- hpc
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100