-
-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
expose_functions errors after update to 2.33 #845
Comments
The error seems to be coming from |
Not sure why but finding the first function declaration returns NA now: # this now returns NA_integer_
first_decl <- grep(paste0(fun_name,"\\("), model_lines)[1] Edit: the reason is that
but |
we should probably run cmdstanr unit tests against the release candidate version of cmdstan going forward so we can catch this sooner |
I'm guessing this is because of stan-dev/stanc3#1313 which @andrjohns requested to make this feature easier for cmdstanr We do run the cmdstanr unit tests during the release candidates, it's not always clear if the failures are significant - this time a few looked like they were due to the deprecations |
Yeah that looks like it would cause the issue I'm seeing. Thankfully this doesn't affect running any models. But it does cause a bunch of unit tests to fail that aren't just due to the deprecations: https://github.com/stan-dev/cmdstanr/actions/runs/6114306271/job/16595596153?pr=843#step:13:3398 |
Closing now that #843 was merged |
Describe the bug
@andrjohns I can't expose stan functions anymore after installing 2.33. Have you run into this? Or any ideas what's going on?
To Reproduce
The example at
?expose_functions
now errors when it didn't before:Expected behavior
No error
Operating system
Mac Big Sur
CmdStanR version number
Current master branch (v 0.6.1.9000)
The text was updated successfully, but these errors were encountered: