Thanks for the feedback.
5.1.3 and 4.3.10 have been released, addressing this issue.
5.2-M1 will not be fixed. The fix is merged on main and part of the daily snapshots. M2 will contain the fix as well.
4 Likes