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

R Markdown and Shiny apps fail with UNC-formatted paths #4807

Closed
ronblum opened this issue May 17, 2019 · 4 comments
Closed

R Markdown and Shiny apps fail with UNC-formatted paths #4807

ronblum opened this issue May 17, 2019 · 4 comments
Labels
bug regression stale windows

Comments

@ronblum
Copy link
Contributor

@ronblum ronblum commented May 17, 2019

System details

RStudio Edition : Desktop
RStudio Version : 1.2.1335
OS Version      : Windows 10
R Version       : 3.6.0

Steps to reproduce the problem

  1. Set the working directory to a path in UNC format.
  2. Create a Shiny app or R Markdown file—the defaults work well.
  3. Save the file in a directory using UNC format.
  4. Knit the R Markdown file or run the Shiny app.

Describe the problem in detail

The process will fail.

Shiny:

> runApp('')
Error in shinyAppDir(x) : No Shiny application exists at the path ""

R Markdown:

<snip>
pandoc.exe: unc.utf8.md: openBinaryFile: does not exist (No such file or directory)
Error: pandoc document conversion failed with error 1
Execution halted

This may be a problem with other file/process types, but these were the ones I tried.

Describe the behavior you expected

Shiny apps should run and R Markdown files should be knittable. Workaround: map a drive to the network drive and use it instead.

There are several known issues with UNC paths, such as #3105 and #4137. However, those were preexisting issues. This one is a regression—it works in 1.1.463.

@rubayat38
Copy link

@rubayat38 rubayat38 commented Mar 24, 2020

Anyone tried to resolve this issue?

@adam-sampson
Copy link

@adam-sampson adam-sampson commented Jul 23, 2020

This problem is related to: rstudio/rmarkdown#701

A dirty workaround is to render to your hard drive and then copy the output from your hard drive to your network drive. You can do this with code by running the following in your console or creating another file RenderMarkdown.R to source.

You MUST create the folder on your hard drive BEFORE you run this code snippet. It doesn't create the folder for you. Feel free to add that to your code if you want. Also note that many organizations that use UNC or NSF also put your Documents and Downloads folder on the network drive...so don't use those as your Intermediates folder.

rmarkdown::render(
"//path/to/file/my_markdown.Rmd",
intermediates_dir = "C:\temp\rmd_knit"
)

@stale
Copy link

@stale stale bot commented Feb 5, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs, per https://github.com/rstudio/rstudio/wiki/Issue-Grooming. Thank you for your contributions.

@stale stale bot added the stale label Feb 5, 2021
@stale
Copy link

@stale stale bot commented Feb 19, 2021

This issue has been automatically closed due to inactivity.

@stale stale bot closed this as completed Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug regression stale windows
Projects
None yet
Development

No branches or pull requests

3 participants