Hey!
Thanks for the report. This is a known issue, and we have a fix for it coming in the next stable release (3.1)!