-
-
Notifications
You must be signed in to change notification settings - Fork 879
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
opts_current locking in 1.44 is breaking JuliaCall #2295
Comments
I tend to change the error to warning for now. |
…king (#2296) Co-authored-by: Yihui Xie <xie@yihui.name>
Perhaps knitr could rely on JuliaConnectoR instead of JuliaCall? https://cran.r-project.org/web/packages/JuliaConnectoR/index.html JuliaCall doesn't seem to be actively maintained, whereas JuliaConnectoR is actively maintained and seems much better documented (for example, it now has a detailed JSS paper). |
@bschneidr The status of JuliaCall is indeed a little concerning, but the nice thing is this: https://github.com/Non-Contradiction/JuliaCall/blob/master/R/RMarkdown.R i.e., it has provided an engine function that can be set via |
@bschneidr I would advise opening an issue at https://github.com/stefan-m-lenz/JuliaConnectoR for a julia engine for knitr. We can then chime in if help is needed for that. Thank you ! |
This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://yihui.org/issue/), and link to this old issue if necessary. |
Upstream has been fixed : |
Great! Thanks for the heads up! |
@yihui Just to track this in order to help them solve this as for now CRAN version of Julia does not work with knitr 1.44 when plots.
it came up in
after the impact of
JuliaCall is using
opts_current$set
, so they need to update but it seems they did not see problem yet.https://github.com/Non-Contradiction/JuliaCall/blob/c05473bea78a0197c639f7e82ab1c6f2e943e1cc/R/RMarkdown.R#L56C1-L60
It seems there is a stale maintenance question though there...
So hopefully we can help.
We could go through a basic search list to see which tool can be impacted (https://github.com/search?q=%22opts_current%24set%22+language%3AR&type=code)
The text was updated successfully, but these errors were encountered: