Cell error traceback incorrectly lexed as IPython

[clarksmr]

Describe the bug

I'm using Jupyter Book to produce a book with executable OCaml cells, including demoing some OCaml code that deliberately does not compile. I tag those cells with raises-exception of course. Some (not all) OCaml compiler error messages cause Sphinx to produce a lexer warning, Could not lex literal_block as "ipythontb".

This bug was reported in MyST-NB as https://github.com/executablebooks/MyST-NB/issues/341. Apparently it was fixed there but Jupyter Book has not yet adopted that fix. So I am now reporting the bug here.

Reproduce the bug

See https://github.com/executablebooks/MyST-NB/issues/341

List your environment

See https://github.com/executablebooks/MyST-NB/issues/341

[welcome[bot]]

Thanks for opening your first issue here! Engagement like this is essential for open source projects! :hugs:
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).
Welcome to the EBP community! :tada:

[stepanzh]

Bump. I'm using Julia in code cells. Same issue for code-cells tagged with raises-exception.

Jupyter Book      : 0.15.1
External ToC      : 0.3.1
MyST-Parser       : 0.18.1
MyST-NB           : 0.17.2
Sphinx Book Theme : 1.0.1
Jupyter-Cache     : 0.6.1
NbClient          : 0.7.4