@tgerz @jbrewer The team is already aware as of yesterday, and is working on a fix. Thanks.