ERROR: AlreadyExists: ... (the error 183) to book project on google drive folder

[jefferds]

when I use a folder on google drive for the book projects I get the following: ERROR: AlreadyExists: ... (the error 183) ... mkdir 'H:\My Drive\001-Projetos...\site_libs\quarto -nav'. Does anybody know how to solve this?

[mcanouil]

You have to give more if you want an actual answer.
Here, you don't provide anything beside an error, no context, no code.
Please do provide some context. 😉

[mcanouil]

Basically, what Quarto version are you using? Are you using Quarto CLI directly or through RStudio, the quarto R package, the Python library, etc.
Describe what you did, such as the commands/functions you used, the tools you used, etc.
The idea is to allow others to reproduce your error.

[jefferds]

Google Drive - v63.0.5.0
Quarto - v1.1.189-win
VSCode - v1.71.0
Quarto extension - v1.38.0

I followed the steps:
quarto create-project mybook --type book
quarto preview

The book is created and opens normally, but when I try to navigate to Introduction or Summary I get the error. The error only occurs if the book is created in a synced Google Drive folder.

[jefferds]

Watching files for changes
Browse at http://localhost:5239/
GET: /
ERROR: AlreadyExists: Não é possível criar um arquivo já existente. (os error 183), mkdir 'H:\Meu Drive\mybook\site_libs\quarto-nav'
GET: /intro.html
GET: /
ERROR: AlreadyExists: Não é possível criar um arquivo já existente. (os error 183), mkdir 'H:\Meu Drive\mybook\site_libs\quarto-nav'
GET: /intro.html
GET: /
GET: /
ERROR: AlreadyExists: Não é possível criar um arquivo já existente. (os error 183), mkdir 'H:\Meu Drive\mybook\site_libs\quarto-nav'
GET: /summary.html
ERROR: AlreadyExists: Não é possível criar um arquivo já existente. (os error 183), mkdir 'H:\Meu Drive\mybook\index_files\mediabag'
GET: /

[mcanouil]

Could you post that on the opened issue? #2174

Also, Do you have the same error in a directory not in Google Drive (or any other cloud framework)? See #2395 for other related Google Drive issues.

@dragonstyle I am pinging you because of #2395 since #2174 might be related. (Maybe closing the discussion to continue on the issue).

[cderv]

Thanks @mcanouil, let's lock the thread here and continue in the issue. Thanks !

[cderv]

Related issue on this #2174