Enable more verbose logging?

[ciaransweet]

Hey folks,

Is there any chance we can enable more verbose logging of the render action?

I've had a run sat doing seemingly nothing for ~10/15 minutes:

Trying to decipher what is happening!

Thanks 🎉

[cderv]

You can activate the same logging as available in quarto CLI applied locally.
https://quarto.org/docs/troubleshooting/#verbose-mode

so setting

env:
  QUARTO_LOG_LEVEL: DEBUG

can give you more information.

However, from the screenshot, I am thinking maybe it is a jupyter execution level.

For that they are debug mode for execution too
https://quarto.org/docs/troubleshooting/#debugging-jupyter-engine-issues

But I realize there is no way to activate it by env var - only CLI flag or through the YAML confuguration.

Also, not related to quarto, but for debugging workflow in an interactive manner, using tmate to connect using SSH to your runnner can be useful: https://github.com/mxschmitt/action-tmate

Hope it helps

[ciaransweet]

Thanks, I switched to raw invocation of the CLI with the debug flags and still nothing once it just sits there 😅

I think I will debug locally and see what's up. It just doesn't want to say it's doing anything and my actions bill is paying for it haha

[cderv]

Sorry for that. It may means that this is something getting on hang at Jupyter evaluation level somehow... If you don't get any log from Quarto and it gets stuck at juypyter evaluation. !
In that case, the execute debug log could help.

Hopefully you'll have more information locally.

[ciaransweet]

Going to close this as it's clearly not an action issue! Though still not much wiser as to what is hanging 😄

[cderv]

If you need any help trying to debug this, please do keep sharing here, and I'll do my best!