Yes, I did not get to fix it before the build was up. There is a new canary build that has a fix for this: