[KNOWN BUG] Template renderer crashes with unhandled traceback on non-UTF-8 files

[simonsigre]

When a template file or XQL snippet contains non-UTF-8 bytes (e.g. content copied from a PDF or Word document), the summon template command crashes with a raw Python traceback. The error message gives no indication of which file or line caused the problem.
Fixed by catching encoding errors and reporting the file name, line number, column, and the offending character position.

Will be fixed in next release

[simonsigre]

When a template file or XQL snippet contained non-UTF-8 bytes, the sort of trash you get from copying content out of a PDF or Word document, the summon template command would crash with a raw Python traceback and no useful context about what went wrong. Fixed by catching encoding errors at the point of file reading and reporting the offending file name, line, column, and character position so you can actually find and fix the problem.

Resolved in v1.22.0-beta.1 (not currently :LATEST tag ) so anyone keen to test try this;

docker pull gocortexio/spellbook:1.22.0-beta.1