This should now be fixed.
not deployed yet? cause It still occurs: 87f7580a0ad64896ba2a093b24fd98e3$aef28e455d57ea7f36604040f32f8352
We're still getting this error. We'll need to do more investigation.
Issue #7090 was marked as a duplicate of this issue.
Please, fix it!
OK, this time we really think it should be fixed.