quarto-dev / quarto-dev/quarto-cli

Build and Render fail when project is on SMB share

Open
#2,380 15 comments 1 reaction 1 assignee View on GitHub

Nobody has claimed this yet.

bug file-systems windows
Dominant language
JavaScript
Stars
6k
Forks
458
Avg merge
1d 9h
Merged PRs (30d)
41

Description

Bug description

I've tried both book and website projects (essentially the same, I know) on both my work and home systems. Both projects build successfully on local storage. Attempting to preview or render the projects on the SMB share fail with different error messages. Rendering individual files succeeds on the SMB share.

Below is the error generated when trying to render a website or book. This error prints in the Background Jobs tab.

ERROR: No valid input files passed to render
Error in get_parentpid() : attempt to apply non-function
Calls: sourceWithProgress ... rstudio_stdout -> rstudio_detect -> detect_new -> get_parentpid
Execution halted

Some more insight is provided by the below preview error message printed to the console:

ERROR: NotFound: The system cannot find the path specified. (os error 3), stat 'UNC\TRUENAS\Files\guslipkin\guslipkin.github.io'
Error in run_serve_daemon("preview", file, NULL, args, render, port, host,  : 
  Error starting quarto

System:

  • RStudio 2022.07.1 Build 554
  • R 4.2.1
  • Quarto 1.1.179 and 1.1.189
  • Windows 10 accessing a SMB share

Reproducible example: My website

I'm happy to do more troubleshooting as needed.

Checklist
  • Please include a minimal, fully reproducible example in a single .qmd file? Please provide the whole file rather than the snippet you believe is causing the issue.
  • Please format your issue so it is easier for us to read the bug report.
  • Please document the RStudio IDE version you're running (if applicable), by providing the value displayed in the "About RStudio" main menu dialog?
  • Please document the operating system you're running. If on Linux, please provide the specific distribution.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.