This was fixed upstream and the fix deployed.
@Torikeshi you have a different problem. I opened a separate thread for that.