I think we fixed this bug in commit 013aabdc665e4256b38d which would have been in the 3.1.0 release (this is why we closed #1774677, which as you say is the same issue).
I think we fixed this bug in commit 013aabdc665e425 6b38d which would have been in the 3.1.0 release (this is why we closed #1774677, which as you say is the same issue).