The fix for this was certainly in the 0.8.1.3 release. Feel free to re-open if you still encounter this bug, though!
The fix for this was certainly in the 0.8.1.3 release. Feel free to re-open if you still encounter this bug, though!