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
There is this weird bug (that I cannot reproduce outside of a very specific environment) when restoring a package from renv.
Basically, build.rs is unable to get the R version due to a NULL being printed before the version. There is no global R profile. The package install ok with remotes (even when renv is initialized).
I think we could fix this by running this in a while loop or using an iteraton while a skip while.
The text was updated successfully, but these errors were encountered:
I'm wondering if semver would be better to use here as a build dependency. it could probably reduce the total amount of code required to parse the R version
I'm wondering if semver would be better to use here as a build dependency. it could probably reduce the total amount of code required to parse the R version
I wouldn't think so. semver has a lot of code to it. I think the current implementation is ok. Semver would not fix the handling of edge cases such as this
There is this weird bug (that I cannot reproduce outside of a very specific environment) when restoring a package from
renv
.Basically,
build.rs
is unable to get the R version due to aNULL
being printed before the version. There is no global R profile. The package install ok withremotes
(even when renv is initialized).I think we could fix this by running this in a while loop or using an iteraton while a skip while.
The text was updated successfully, but these errors were encountered: