Closed leungi closed 4 years ago
This is expected. rsconnect
relies on Packrat to infer an application's R package dependencies, and this will fail if you load your packages in creative ways.
The diagnostic report at the end of the deployment is accurate and indicates how the problem can be fixed.
Noted; will stick with library()
.
Thanks for prompt reply.
I'm glad I could help!
As an aside, I think I may off been a bit curt in my reply; I'm sorry for that. The crux of the matter is indeed that we do rely on static analysis of the R code in an application in order to infer the application's R package dependencies, and that static analysis does fail when packages are loaded in non-typical ways.
@kevinushey: Appreciate your consideration; I'm not offended at all 😉.
I totally fail on K.I.S.S. principle!
Both methods below work in interactive session, but method 2 fails when deploying via RS Connect.
1) This works, as expected
2) This fails
RS Connect log