FWIW, this was fixed in upstream commit

441f0e0d84082eb498e620327ebf4de509052d15

So ever since 2.2.17.rc1

Jason

Reply via email to