release = TRUE error
Open
Nobody has claimed this yet.
- Dominant language
- TeX
- Stars
- 7
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
Tom had the following error when he tried grattanReporter(compile = TRUE, pre_release = TRUE, release = TRUE).
No such error with grattanReporter(compile = TRUE, pre_release = TRUE)
Error: /undefinedfilename in (Report.pdf)
Operand stack:
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push
Dictionary stack:
--dict:726/1123(ro)(G)-- --dict:0/20(G)-- --dict:75/200(L)--
Current allocation mode is local
Last OS error: No such file or directory
GPL Ghostscript 9.50: Unrecoverable error, exit code 1
Error in gettextf("status %d in running command '%s'", ret, cmd) :
object 'cmd' not found
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
Start at the grattanReporter entry point and reproduce the failure with compile = TRUE, pre_release = TRUE, and release = TRUE. Compare that path with the working pre_release-only path, focusing on how Report.pdf is passed to Ghostscript. Done means release = TRUE completes without the undefinedfilename error while the existing pre-release behavior still works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- r, tex
- Domain
- build-system, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100