[makeinstancesufo] continue when failing on one UFO?

[frankrolf]

I wanted to add this to #1145 since it’s related, but I assume a new bug is better:

Currently, when makeinstancesufo fails for a given instance, it’ll stop right there and leave me to figure out what the problem might be. In a typical git environment, this will lead to thousands of files changed, which are effectively noise until I can figure out what the problem is.

Would it be possible to make the instance generation move on regardless of an individual failure, and show a report at the end?

File under “one can dream”: perhaps the solution to this would also allow us to think of using multiple threads for makeinstancesufo?

[frankrolf]

A workaround I am using for this is

for i in $(seq 0 29); do makeinstancesufo -v -i $i -d SourceSerif4.designspace; done

[josh-hadley]

@frankrolf Does the implementation of multiprocessing in makeinstancesufo address this?