[interpolation_issues] chokes on component heavy font without error

[kontur]

Observed behaviour

A pixel-component font like Handjet causes this check to get stuck.

Note that the font is has each individual letter composed from a "pixel" component, so may include dozens of components for all of its glyphs. While interpolation checks for the positions of the pixel component may, as such, be useful for a font like this as well, it is likely that this check should not run for a font constructed like this, i.e. with a large amount of components for all glyphs.

Expected behaviour

Not choke or exit with warning.

I expect this to be such an edge case that the check itself doesn't necessarily need to perform a sanity check to avoid this situation, but the expected use might be to exclude this check. However, the CLI just getting stuck without any output should not happen.

Resources and steps needed to reproduce

1. Download Handjet
2. pip install fontbakery==1.0.0
3. fontbakery check-universal Handjet\[ELGR,ELSH,wght\].ttf -c interpolation_issues -l DEBUG

The command line will just be stuck without output or error.

[simoncozens]

It's neither choking or getting stuck; it's checking the font for interpolation issues, like you asked it to. If you don't want it to do that, don't run the check - you can exclude it in a configuration file or on the command line.