On 9/27/24 11:28 AM, Jiri Denemark wrote:
Please give the release candidate some testing and in case you find a serious issue which should have a fix in the upcoming release, feel free to reply to this thread to make sure the issue is more visible.
Last night I discovered a regression caused by my commit a37bd2a15b8f2e7aa09519c86fe1ba1e59ce113f pushed a few weeks ago. I have a very simple patch that eliminates the regression, but doesn't fix the larger problem - that is going to require much more thinking than is available in this time frame.
I'll be posting the patch shortly (while simultaneously running it through CI and doing more testing). The alternatives to this would be:
1) revert the earlier patch (but I haven't checked yet if this is going to conflict with / functionally break the other patches in that series, or
2) leave this regression in the release
