Skip to content
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

renv::auto_load does not work anymore #1580

Closed
jd4ds opened this issue Jul 24, 2023 · 1 comment · Fixed by #1584
Closed

renv::auto_load does not work anymore #1580

jd4ds opened this issue Jul 24, 2023 · 1 comment · Fixed by #1584
Labels
bug an unexpected problem or unintended behavior

Comments

@jd4ds
Copy link

jd4ds commented Jul 24, 2023

Hey,
I think with this commit (314009b#diff-43c4528da3e8c329bb7bce6306f225c0b66b8e8c2fdc8d5f5f2560df86542707) a logic error has been inadvertently introduced into the autoload function, which causes the trigger for autoload to work the other way around.
If RENV_AUTOLOAD_ENABLED=TRUE or not set, the autoload operation is aborted instead of being performed.
This is currently causing a problem in our build pipelines and on Posit Workbench that all projects are running against the standard R library and are no longer initializing with locked packages or tracking changes.
I would be very grateful for a quick fix.
Thanks and best regards!

@kevinushey kevinushey added the bug an unexpected problem or unintended behavior label Jul 24, 2023
@kevinushey kevinushey added this to the 1.0.1 milestone Jul 24, 2023
@kevinushey
Copy link
Collaborator

Thank you for the bug report! You're right about the error; we'll get this fixed up soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug an unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants