What a coincidence! The same bug was just reported here yesterday and I merged a fix a couple of hours ago:
Thanks for reporting!