-
Notifications
You must be signed in to change notification settings - Fork 154
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
Failed to parse 'renv.lock' #2091
Comments
This looks similar to an issue I have been having #2089 . |
This issue should now be fixed in the development version of renv::install("rstudio/renv") then, restart R and see if you're now able to call |
Thank you for your development. I just tried with the new |
Can you try placing the following in your project's library(utils)
Rprof("startup.Rprof")
source("renv/activate.R")
Rprof(NULL)
summaryRprof("startup.Rprof") Then, restart your R session. You should see a print-out of what functions were executed, and what took the most time. Can you share that? |
Here are the outputs of the Rprof part . |
Thanks -- it looks like BiocManager is the culprit. Unfortunately it wants to make a web request just to determine if the current version of R is compatible with the version of Bioconductor being used... I'll see if I can work around this. |
I've just pushed a potential fix for this issue -- can you try once more installing the development version of renv::install("rstudio/renv") |
I thought it was fixed in a previous version without updating |
Yes it looks ok for me. No error message anymore to parse |
Great, thanks for confirming. I'll try to get an update to CRAN early next week. |
I tried to use the version 1.1.1 version of the renv package. After executing the renv::snapshot() command, when I open the project I get the following message :
Error in (function (err) : Failed to parse 'renv.lock':
input string 1 is invalid UTF-8
Here are the session information :
In the attached file, you can find the content of the renv.lock file.
renv_lock.txt
The text was updated successfully, but these errors were encountered: