Sorry for the trouble. We already have a fix for it internally. It just needs to go through some testing before we release it,