Closed slodge closed 3 years ago
Sure I'll get that fixed. I'm a bit surprised that it errors, I guess it is unusual for the files in your home dir to not be writable.
Can you test if it works now?
Wow. Thanks.
In the middle of a meeting - can check in next 6 hours
Tested using install_github
It works - such a quick turnaround - thanks 👍
Log of install was:
2021-04-20T19:14:08.2986730Z 2021/04/20 19:14:07.022863601 Installing credentials (1.3.1) ...
2021-04-20T19:14:09.7483393Z 2021/04/20 19:14:07.493751481 curl: HTTP 200 https://codeload.github.com/r-lib/credentials/legacy.tar.gz/721bef312cc7a6fc0b77280e14b040aedd660e6c
2021-04-20T19:14:13.7984754Z 2021/04/20 19:14:11.522792387 Caching credentials.
2021-04-20T19:14:13.7985216Z 2021/04/20 19:14:11.531862557 Using cached credentials.
2021-04-20T19:14:13.7986136Z 2021/04/20 19:14:11.533879209 OK (built source)
👍
Currently we have an issue where rsconnect/packrat are somehow insisting on publishing
credentials
as a dependency of one of our applications.The problem with this is that
credentials
won't install in the restricted (sandboxed) security space that we're running RStudio Connect installation.Example part of our application publish logs:
I'm not entirely sure still of quite how/why
credentials
is being pulled into one of our applications which is being deployed into our RStudio Connect server... and I am digging into that - see some notes on https://github.com/rstudio/rsconnect/issues/505However, I was also wondering if
credentials
would be interested in a PR which would allowcredentials
to fail with warnings rather than errors inonLoad
https://github.com/r-lib/credentials/blob/17eaef8f811f0be4f2eebbfd7ac6f2c9939e9af7/R/onattach.R#L3 ?