Changes to stan models in source not recognized -- "make: Nothing to be done for 'all'."
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- r
- Domain
- build-system, tooling
Research direction
Start by reproducing the issue in an R package that uses rstantools: change a Stan source file, run rstan_config(), and build while checking whether the changed source is present. Compare that with deleting the relevant generated source files before building; done means changes to Stan files reliably trigger compilation without manual deletion.
Written by the indexing model from the issue text.
Description
When building ctsem (using rstantools), I'm encountering this all of a sudden -- after some small changes to the stan files, I run rstan_config() and double check that the source files are changed, but when I build, compilation is for some reason not triggered. If instead I delete the relevant source files and build, compilation works normally and everything is as expected. Any ideas welcome...
- Dominant language
- R
- Stars
- 49
- Forks
- 24
- Avg merge
- 23h 46m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from stan-dev/rstantools
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
stan-dev/rstantools#131 · 2 comments ·
-
Use testthat 3eMay be free again @VisruthSK claimed this 72 days ago, and no pull request is open. Open
stan-dev/rstantools#159 · 1 reaction · 1 assignee ·
-
Cleanup VignetteMay be free again @VisruthSK claimed this 75 days ago, and no pull request is open. Open
stan-dev/rstantools#157 · 1 comment · 1 assignee ·
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
stan-dev/rstantools#134 · 6 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
stan-dev/rstantools#128 · 1 comment ·
All issues in stan-dev/rstantools
Similar issues
-
[work-item] adam-adae-serious-events: pin missing-AESER filter semanticsPossibly taken @muse-yamaa-bot claimed this today. Openwork-item
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
rfordatascience/tidytuesday#1089 ·
-
Component: R Type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/arrow#51695 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nflverse/nflverse-rosters#102 ·
-
bug priority: should
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
The-Strategy-Unit/nhp_outputs#477 ·