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
Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.
If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).
Is it possible that the traceback is not showing because nb_execution_raise_on_error = True (cf. #531)? A workaround for me has been to leave nb_execution_raise_on_error = False but invoke Sphinx with the -W flag which turns warnings into errors.
As discussed in #531 (comment), I think you just need to turn on nb_execution_raise_on_error, and run sphinx-build with -T in order for this to work. The nb_execution_show_tb option seems like a workaround for cases when we don't have access to sphinx-build arguments, in which case #482 (comment) is the appropriate usage.
However, #531 has merged, so in future nb_execution_raise_on_error should have no effect upon nb_execution_show_tb.
Describe the bug
context
When I set
nb_execution_show_tb = True
in myconf.py
and my CI build fails, no exceptions are printed.Possibly relevant packages installed by CI:
Reproduce the bug
Make a failing
.md
file and observe the absence of exceptions in the logs.List your environment
Can't run this in CI.
It is installing latest versions.
The text was updated successfully, but these errors were encountered: