@arkisling - thanks for the report. I’ve just uploaded a fix for this right now as part of the v1.1 release.