I’m not sure when this appeared. Maybe after last upgrade. Is it OK to ignore?
I’ll have a look. Might have missed this case.
Just pushed a fix