rstudio / promises

A promise library for R
https://rstudio.github.io/promises
Other
198 stars 19 forks source link

I can't run Shiny apps after installing promises and async shiny #12

Closed dgyurko closed 6 years ago

dgyurko commented 6 years ago

Running any Shiny app aborts the session for me, after installing the promises and the async version of shiny packages using the following commands:

devtools::install_github("rstudio/promises")
devtools::install_github("rstudio/shiny@async")

I am using RStudio Version 1.1.419 My sessionInfo():

R version 3.4.1 (2017-06-30)
Platform: x86_64-w64-mingw32/x64 (64-bit)
Running under: Windows >= 8 x64 (build 9200)

Matrix products: default

locale:
[1] LC_COLLATE=Hungarian_Hungary.1250  LC_CTYPE=Hungarian_Hungary.1250    LC_MONETARY=Hungarian_Hungary.1250 LC_NUMERIC=C                      
[5] LC_TIME=Hungarian_Hungary.1250    

attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods   base     

other attached packages:
[1] shiny_1.0.5.9000    promises_0.1.0.9001

loaded via a namespace (and not attached):
 [1] Rcpp_0.12.15       digest_0.6.15      later_0.7.1        mime_0.5           grid_3.4.1         plyr_1.8.4         R6_2.2.2           xtable_1.8-2      
 [9] gtable_0.2.0       magrittr_1.5       scales_0.5.0.9000  ggplot2_2.2.1.9000 pillar_1.0.1       rlang_0.1.6        lazyeval_0.2.0     tools_3.4.1       
[17] munsell_0.4.3      httpuv_1.3.5.9005  yaml_2.1.16        compiler_3.4.1     colorspace_1.3-2   htmltools_0.3.6    tibble_1.4.1 
jcheng5 commented 6 years ago

Is this still happening for you?

dgyurko commented 6 years ago

Yeah, it still persists.

Also I can't load shiny after removing promises and replacing the async version of shiny:

Error: package or namespace load failed for ‘shiny’ in loadNamespace(j <- i[[1L]], c(lib.loc, .libPaths()), versionCheck = vI[[j]]):
 there is no package called ‘promises’

It should probably remove promises from the package dependency of shiny when removing promises.

dgyurko commented 6 years ago

Just checked again, and it seems to be working now. Keep up the good work!