Note that the fix is in 4.26. Since this issue is a lot more wide spread than we thought I’ll merge the fix to 4.25.1.