Thanks for the report, this bug is already fixed internally and the fix will be part of the next update in the coming days! :)
