Better jinja errors about www HOT 5 CLOSED

Maybe. It's almost certainly coming from the conf.py, but guessing it's run in some undefined context.

from www.

Most likely to be in load_conference_context_from_yaml in _ext/core.py after @mxsasha 's refactor a while back?

from www.

Do you have an example of a build that failed on this? Then I can mess around with it and see if we can print more context. Looked through some recent failures but did not see this type.

from www.

I thought it was one of the recent broken ones in the Australia PR, but all I'm getting now is this

Handler <function render_rst_with_jinja at 0x7fc53fd82b00> for event 'source-read' threw an exception (exception: include/schedule2022.rst)

in 0908bf2

from www.

I can't reproduce that last one, as the branch is gone.

For the initial error about unconf being undefined: #1833. Line numbers are not available in the error.
The root cause here is that our YAML validator is quite flexible, to allow historical YAML files too. We could make a separate schema for newer files, or just make a stricter schema and only validate newer files, as the old ones don't really change.

from www.