It turns out the issue I was seeing was caused by a patch I was testing for bug 2003250. Without that, this patch works as expected.
It turns out the issue I was seeing was caused by a patch I was testing for bug 2003250. Without that, this patch works as expected.