 This was likely related to #67 but that's now fixed.