You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've noticed the above error in some of our scheduled jobs using QuartoNotebookRunner.jl. Error: ArgumentError: input string is empty or only contains whitespace
Turns out when a worker crashes before a port is written back, stdout is read back as "" so you get an error when parsing that as the port number.
We haven't figured out how to reliably reproduce it + we cannot debug it without insight into the Malt worker failure.
It failed several times but always at a different point (different notebooks, so it's not data problem).
Temporary solution: Remove outer asyncmap and run serially
Oddly, it was running fine for 7 days after upgrading to Julia 1.11 (and quarto 1.7.2, containing QuartoNotebookRunner 11.6?).
Reproduction:
Our setup is similar to the following (notebooks are in different folders not to clash in Quarto production):
asyncmap(1:100; ntasks=3) do i
run(`quarto render notebook_$(i)/notebook.qmd`)
end
No, we're not setting any exeflags. The process runs and has been running for a week.
Today was the first day it failed with this error (and repeatedly). It's just weird flukes that happened at different times/files.
We produce c. 30 notebooks, each takes ~1-2 mins and we were running 3 in parallel (ntasks=3), so it seems unlikely they all hit some file/lock exactly at the same time.
You could try cloning QuartoNotebookRunner somewhere, then dev'ing JuliaPluto/Malt.jl#85 into it, then using it for quarto by setting QUARTO_JULIA_PROJECT="the/path/to/quartonotebookrunner". That might give you the specific underlying error?
We've noticed the above error in some of our scheduled jobs using QuartoNotebookRunner.jl.
Error: ArgumentError: input string is empty or only contains whitespace
This seems similar to: JuliaPluto/Malt.jl#85 where it says
We haven't figured out how to reliably reproduce it + we cannot debug it without insight into the Malt worker failure.
It failed several times but always at a different point (different notebooks, so it's not data problem).
Temporary solution: Remove outer
asyncmap
and run seriallyOddly, it was running fine for 7 days after upgrading to Julia 1.11 (and quarto 1.7.2, containing QuartoNotebookRunner 11.6?).
Reproduction:
Our setup is similar to the following (notebooks are in different folders not to clash in Quarto production):
The text was updated successfully, but these errors were encountered: