This issue has been addressed in v1.8.2, released on Thu 1/3/2019.

Did this answer your question?