-
Notifications
You must be signed in to change notification settings - Fork 24
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
quarto::render() fails in parallel il project.render is "*.qmd" #224
Comments
Is everything running in same working directory ? It seems that all This does not seem like something that will work very well unfortunately. Though, I understand this works ok for you except using Stack Trace shows that the problem happens while resolving and expanding the glob, which is directly related to It seems directly related to conflict between processes because a path to mediabag dir like I see in Deno's code for let fixedRootInfo: WalkEntry;
try {
fixedRootInfo = createWalkEntrySync(fixedRoot);
} catch (error) {
return throwUnlessNotFound(error);
} But some other times they don't like in if (includeDirs && include(root, exts, match, skip)) {
yield createWalkEntrySync(root);
} So it seems like a Deno bug at the root when running in parallel some deno process that will try to read / write / remove /expand same path at different times. Not sure exactly what Quarto should do here - especially since we know that |
Hello, Yes, the rendering is done from the same working directory. Here is a reprex (with a Github action) of the code provided in the issue : https://github.com/ColinFay/quartoreprex/actions/runs/13507065321 And yes, this does work if there is no |
Sad that we are hit by this Deno behavior then... Not sure how to prevent it. 🤔 |
Bug description
Rendering in parallel fails if
project.render
is"*.qmd"
in_quarto.yaml
Reprex
Let's assume the following
_quarto.yaml
:Which is found on the doc at https://quarto.org/docs/projects/quarto-projects.html#render-targets
If I create a series of qmd and tries to render them in parallel using
{future}
, it fails :With the following error:
Notes
Removing the
_quarto.yml
worksA
_quarto.yml
with other content will workSession information
The text was updated successfully, but these errors were encountered: