Just as a general note, this is in regards to an old bug from 2019 that has long been fixed. You are probably looking for this report instead.
And as noted there, the issue has been filed and fixed internally. We know what is wrong and require no further information.