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

Generating pandoc error when trying to launch Scenario Explorer #22

Closed
lanceDamage opened this issue Feb 10, 2018 · 7 comments
Closed

Comments

@lanceDamage
Copy link

lanceDamage commented Feb 10, 2018

I am trying to launch Scenario Explorer and I am getting the following error in my browser:

"Error: pandoc document conversion failed with error 1"

Alicia explains very well why this happens when transitioning from an html document: ropensci/iheatmapr#4
This did not work: Alternative fix involving removing of Pandoc: rstudio/rmarkdown#1184 [devtools::install_github('rstudio/rmarkdown')]
Alternative fix involved installing a markdown package found here: https://stackoverflow.com/questions/47323389/pandoc-document-conversion-failed-with-error-1-after-update-to-r-version-3-4-2

@lanceDamage
Copy link
Author

sessionInfo()
R version 3.4.1 (2017-06-30)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS High Sierra 10.13.3

Matrix products: default
BLAS: /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/3.4/Resources/lib/libRlapack.dylib

locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8

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

other attached packages:
[1] pander_0.6.1 tidyr_0.8.0 psych_1.7.8 purrr_0.2.4 ggalt_0.4.0
[6] extrafont_0.17 ggplot2_2.2.1 viridis_0.5.0 viridisLite_0.3.0 scales_0.5.0
[11] bindrcpp_0.2 evaluator_0.1.1 readr_1.1.1 dplyr_0.7.4 shiny_1.0.5

loaded via a namespace (and not attached):
[1] maps_3.2.0 purrrlyr_0.0.2 jsonlite_1.5 assertthat_0.2.0
[5] highr_0.6 cellranger_1.1.0 yaml_2.1.16 Rttf2pt1_1.3.5
[9] pillar_1.1.0 backports_1.1.2 lattice_0.20-35 glue_1.2.0
[13] extrafontdb_1.0 digest_0.6.15 RColorBrewer_1.1-2 colorspace_1.3-2
[17] htmltools_0.3.6 httpuv_1.3.5 plyr_1.8.4 pkgconfig_2.0.1
[21] flexdashboard_0.5.1 xtable_1.8-2 tibble_1.4.2 DT_0.4
[25] lazyeval_0.2.1 cli_1.0.0 mnormt_1.5-5 magrittr_1.5
[29] crayon_1.3.4 readxl_1.0.0 mime_0.5 memoise_1.1.0
[33] evaluate_0.10.1 ash_1.0-15 nlme_3.1-131 MASS_7.3-47
[37] foreign_0.8-69 tools_3.4.1 hms_0.4.1 stringr_1.2.0
[41] munsell_0.4.3 bazar_1.0.6 kimisc_0.4 compiler_3.4.1
[45] rlang_0.1.6 grid_3.4.1 rstudioapi_0.7 htmlwidgets_1.0
[49] crosstalk_1.0.0 labeling_0.3 rmarkdown_1.8 proj4_1.0-8
[53] gtable_0.2.0 reshape2_1.4.3 statip_0.1.5 R6_2.2.2
[57] gridExtra_2.3 knitr_1.19 utf8_1.1.3 bindr_0.1
[61] rprojroot_1.3-2 KernSmooth_2.23-15 stringi_1.1.6 parallel_3.4.1
[65] Rcpp_0.12.15 tidyselect_0.2.3

@lanceDamage
Copy link
Author

SOLUTION:

In the workflow instructions I suggest fully explaining that Shiny.io needs to be signed up for and that the "rsconnect" package needs to be loaded and a valid token provided.

@davidski
Copy link
Owner

Would you provide the exact command you were running that generated that error? Having Shiny.io credentials should not be necessary for running the standard explore_scenarios function. That Shiny app runs on the local system and shouldn't have any external dependencies. Would like to delve into this more and try to reproduce. Thanks for the report!

@davidski
Copy link
Owner

Hey @lanceDamage. Checking in on this issue. Can you provide the command you were running for explore_scenarios? I'm unable to reproduce and Shiny.IO credentials shouldn't be required for running that function. 😖

@lanceDamage
Copy link
Author

lanceDamage commented Mar 13, 2018 via email

@lanceDamage
Copy link
Author

lanceDamage commented Mar 14, 2018

@davidski , I tried replicating this on the same system, and on an independent Windows 10 system and I couldn't replicate the error. I must assume it was operator error on my part. I'm not having any trouble now with these errors. I think we can close this issue.

@davidski
Copy link
Owner

Darn. I hate those sorts of issues. :/ Glad it's working for you now though!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants