Hello! Thanks for reporting. This bug has been addressed in 0.8.1.6. and should no longer be an issue.
