>>539672734
>said that it was fixed in an internal build