This looks like bug 16158; a fix will be in the next 2.6.x and 3.0.x releases, which are currently scheduled for 2019-12-04.
