Google drive sync issue

[issactoast]

Bug description

After update quarto from 1.2.475 to 1.3.450(or higher version will generate the same error), quarto can't render in Google drive.

Steps to reproduce

1. Create project folder in Google drive
2. Make quarto for word
3. Save and render
4. Result as follows:

Expected behavior

After I uninstall 1.3.x and reinstall 1.2.x, the same qmd can be rendering as follows without an error;

Actual behavior

No response

Your environment

R 4.3.2 RStudio 2023.12.0 Build 369 Quarto version 1.2.475

Quarto check output

A new release of Deno is available: 1.28.2 → 1.40.1 Run `deno upgrade` to install it.

[>] Checking versions of quarto binary dependencies...
      Pandoc version 3.1.1: OK
      Dart Sass version 1.55.0: OK
[>] Checking versions of quarto dependencies......OK
[>] Checking Quarto installation......OK
      Version: 1.3.450
      Path: C:\R\Quarto\bin
      CodePage: 949

[>] Checking basic markdown render....OK

[>] Checking Python 3 installation....OK
      Version: 3.9.7 (Conda)
      Path: C:/R/miniconda3/python.exe
      Jupyter: 4.10.0
      Kernels: python3

[>] Checking Jupyter engine render....OK

[>] Checking R installation...........OK
      Version: 4.3.2
      Path: C:/R/R-4.3.2
      LibPaths:
        - C:/R/R-4.3.2/library
      knitr: 1.45
      rmarkdown: 2.25

[>] Checking Knitr engine render......OK

[ThSGM]

Thank you for reporting this. I was having the same issues and it was driving me crazy.

Two thoughts:

• Is this due to Google's sync app? I think this might be the case because I did not get the error when I turned off the sync app. Also I tested it on smaller projects where the rendering might be done before the sync makes any changes.
• Is it possible that this is due to the sync app deleting files that are being rendered temporarily?

It may be completely unrelated, but I have noticed that when I save files in Mathematica to Google Drive, I would get warning messages. This had to do with Mathematica's built-in file change protection, which needed to be disabled: https://mathematica.stackexchange.com/questions/261481/mathematica-and-google-drive-backup-client

At the moment, pausing any sync for large render jobs seems to be an OK band-aid.