Hey, thanks for reporting! I am uploading a fix for this right now. It was introduced in 0.6.5.9 and slipped our testing. Should be ready to download very soon. :)