You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for creating renv! This is super useful mechanism that we used in many projects!
We appreciate the time and the energy you invested in building the tool.
ver 1.0.10 issue
Recently we noticed some weird behavior for the newly released renv 1.1.0 on Windows.
If you have an exported function called module and it's used in testthat tests,
then when running renv::snapshot() you can see it fails to create the lockfile.
Is it a names collision with modules::module that is used inside renv?
Is it some collision with reticulate/python modules?
Is module a reserved name that is omitted or treated differently by renv?
Note
Suprisingly if you call module function with some custom parameter (like x = 1) then this issue no longer appears and you can crate the lockfile.
But if there is no parameter provided, renv::snapshot fails.
The text was updated successfully, but these errors were encountered:
Thanks for the bug report, and especially for taking the time to provide a reproducible example! This should now be fixed up in the development version of renv; I'll try to get a patch release onto CRAN soon.
m7pr
changed the title
renv::snapshot() fails for 1.1.0 version on Windows if run on a package directory that has an exported function called module()renv::snapshot() fails for 1.0.10 version on Windows if run on a package directory that has an exported function called module()Oct 22, 2024
Since `renv` was released on CRAN on Oct 12
https://cran.r-project.org/web/packages/renv/index.html with the newest
fix for the bug that we reported in here
rstudio/renv#2007 we can just vbump `renv` and
use CRAN version instead of GitHub version.
Signed-off-by: Marcin <133694481+m7pr@users.noreply.github.com>
Thanks for creating
renv
! This is super useful mechanism that we used in many projects!We appreciate the time and the energy you invested in building the tool.
ver 1.0.10 issue
Recently we noticed some weird behavior for the newly released
renv
1.1.0 on Windows.If you have an exported function called
module
and it's used intestthat
tests,then when running
renv::snapshot()
you can see it fails to create the lockfile.The reproducible example can be based on this repository https://github.com/m7pr/renv.modules
Just pull it and run
renv::snapshot()
.That's what I get
ver 1.0.9 no issue
This does not happen on previous version
Potential places for the fix
Is it a names collision with
modules::module
that is used insiderenv
?Is it some collision with reticulate/python modules?
Is
module
a reserved name that is omitted or treated differently byrenv
?Note
Suprisingly if you call
module
function with some custom parameter (like x = 1) then this issue no longer appears and you can crate the lockfile.But if there is no parameter provided,
renv::snapshot
fails.The text was updated successfully, but these errors were encountered: