No I was on vacation and missed that bug. I have forwarded it to the team and it looks like we can fix it with v1.111.