This has been fixed upstream in commit d31ce6b696cdae0e28aca49e0c8887b450114780, from release 3.11.91.
I've also attached the patch of the commit (which applies cleanly to the 3.10.0 code).
This has been fixed upstream in commit d31ce6b696cdae0 e28aca49e0c8887 b450114780, from release 3.11.91.
I've also attached the patch of the commit (which applies cleanly to the 3.10.0 code).