That might work. It seems like the error is coming from somewhere in the
Racket runtime when it tries to load a module, so I don't think there is an
easy way to catch the error and cleanly deal with it.
Thanks,
Basu
On Fri, Jun 28, 2019 at 3:01 PM Matthew Butterick wrote:
> Should -p take an
Should -p take an argument to limit the max number of parallel jobs?
> On Jun 28, 2019, at 11:47 AM, Shrutarshi Basu wrote:
>
> After some more experimentation, it seems like the problem goes away if I
> drop the -p flag. So `raco pollen render -s .` works just fine. My hypothesis
> is that
After some more experimentation, it seems like the problem goes away if I
drop the -p flag. So `raco pollen render -s .` works just fine. My
hypothesis is that when running in parallel mode, the pollen process (?)
opens a lot of files in parallel, which triggers the "Too many open files"
error.
I've managed to fix the publish case so that I no longer see the error. It
is not working the way I would like, but I will send a separate email with
some thoughts on the `render` and `output` commands and their workings.
Here is the code I currently have for my setup:
;; Override Pollen
Thank you! This is very helpful. I'm still trying to figure out what the
good balance between Makefiles and render -p. Some experimenting is in
order.
On Fri, Jun 28, 2019 at 12:47 PM Joel Dueck wrote:
> Take a look at one of my recent Pollen makefiles:
>
Take a look at one of my recent Pollen makefiles:
https://thelocalyarn.com/cgi-bin/yarncode/artifact/7a3d32d6264f1bcb
I define my dependencies such that if one of the core files (like
pollen.rkt) has changed, it triggers a re-render of all documents with
`raco pollen setup` and then `raco
I think I'm somehow creating infinite loops for two different use cases.
First, I have a nested directory structure and I'm trying to run pollen in
parallel subdirectory mode. I'm using `raco pollen -p -s . ` and here is
the error I'm getting:
pollen: rendering generated pagetree for directory
