<guardian>
ddfreyne: unfortunately the issue doesn't link to a commit
louquillio_ has quit [Ping timeout: 240 seconds]
louquillio_ has joined #nanoc
louquillio_ has quit [Ping timeout: 252 seconds]
louquillio_ has joined #nanoc
relix has joined #nanoc
alerante has joined #nanoc
<ddfreyne>
guardian: It is not fixed in nanoc
<ddfreyne>
USR1 is reserved for the JVM and nanoc trying to take control of it fails
<ddfreyne>
That issue is from 5 years ago.
<ddfreyne>
Sorry, 7
alerante has quit [Ping timeout: 252 seconds]
<ddfreyne>
guardian: So disabling it on nanoc+JRuby seems like a decent way forward
relix has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
relix has joined #nanoc
relix has quit [Client Quit]
<prxq_>
guardian: thanks
relix has joined #nanoc
relix has quit [Client Quit]
relix has joined #nanoc
relix has quit [Client Quit]
louquillio_ has quit [Ping timeout: 255 seconds]
louquillio_ has joined #nanoc
cDlm has quit [Quit: Computer has gone to sleep.]
cDlm has joined #nanoc
<cDlm>
what was usr1 used for ?
<guardian>
ddfreyne: yeah I started with the issue in the nanoc PR queue then tried to understand the situation until I found that bug report that pretends it's fixed in JRuby
alerante has joined #nanoc
alerante has quit [Ping timeout: 264 seconds]
cDlm is now known as VitamineD
jugglinmike has joined #nanoc
<guardian>
ddfreyne: so sending USR1 in the middle of a nanoc compile dumps a stack trace?
<guardian>
ddfreyne: or is it intended to send USR1 from within a helper or filter and get the outerloop dump a stack trace?
prxq_ is now known as prxq
alerante has joined #nanoc
VitamineD_ has joined #nanoc
VitamineD has quit [Ping timeout: 265 seconds]
VitamineD_ has quit [Ping timeout: 276 seconds]
<ddfreyne>
guardian: USR1 is used to dump the stack trace. It's useful to find out what nanoc is doing exactly
<ddfreyne>
(It's a nanoc thing)
<ddfreyne>
It's purely a debugging thing. It can be disabled easily
<guardian>
but who sends USR1
<guardian>
and when?
<guardian>
is it you launch nanoc compile and from another term you kill -USR1 nanoc?
<ddfreyne>
guardian: yup
<guardian>
uh!
<guardian>
is it really useful?
<guardian>
like, I launch nanoc compile, at the time kill -USR1 nanoc is fired, I have no idea which stack trace gonna be dumped
<ddfreyne>
guardian: It's useful in a situation where nanoc apparently hangs
<ddfreyne>
If you send SIGUSR1, you'll know where it hangs
<guardian>
ok
cDlm has joined #nanoc
alerante has quit [Remote host closed the connection]
<jugglinmike>
Does anyone here use nanoc inside a VM? Possibly with Vagrant? I'm just setting this up, and seeing a lot of needless re-compilation happening. I'm wondering if this has something to do with the host/guest shared folder syncing
<guardian>
interesting
<guardian>
can you please ping me once you figured that out?
<jugglinmike>
guardian: I'll let you know what I come up with
alerante has joined #nanoc
<jugglinmike>
guardian: User error
cDlm has quit [Ping timeout: 240 seconds]
<jugglinmike>
I still have an `output/` directory on my host machine. Every time I changed something in `content/`, the `output/` on the host was ALSO being rsync'd to the guest, and nanoc (running on the guest) correctly identified that those output files needed to be re-compiled
<jugglinmike>
adding "output/" to the `rsync__exclude` list fixed the problem
<guardian>
ok
alerante has quit [Ping timeout: 264 seconds]
<prxq>
is there a way to do "nested" layouts? I have parts of pages that appear in more than one other page...