by Ken Task.
Yes, it might be a 'bug' ... in your case and in the other user reporting. I just took a 2.3.*highest* to 2.4 and didn't see the same issues. Note: had other issues but those related to 3rd party add-ons (to be expected sometimes).
Did you 'git pull' your 2.3 to bring it up to highest first? The 'bug' might have been cleaned up by doing that. The 'bug' or 'fix' appears to have been lying in wait and not triggered before now.
Doesn't hurt to wait though ... sometimes better safe than sorry! ;)
'spirit of sharing', Ken