Some after-migration messages are semi-attributed to mannequins

[arhadthedev]

Bug occurence 1

There is a message (#91404 (comment)) from a non-core contributor with authorship inconsistence. It's properly attributed to a GitHub user but a big message avatar image is taken from a mannequin.

However, another after-migration message from the same user (#89702 (comment)) has no such an issue.

A screenshot of #91404:

---

Bug occurence 2

A notification on referring from another issue/PR (#91230 (reference)) is fully attributed to a mannequin:

while the referrer isn't and can't because it's a PR:

---

Bug occurence 3

#89279 (comment), the same as occurence 1.

[AlexWaygood]

See also https://discuss.python.org/t/github-issues-migration-mannequin-users/14965

[arhadthedev]

If sampling diversity will help in debugging: #88228 (comment) is affected too showing both problems.

[ezio-melotti]

Thanks for the report. I notified GitHub about the issue.

[hugovk]

When I opened this comment it showed the ghost mannequin icon, but as I was reading, it updated to the real profile image. So I guess it's a caching thing?

[AlexWaygood]

When I opened this comment it showed the ghost mannequin icon, but as I was reading, it updated to the real profile image. So I guess it's a caching thing?

It seems to vary depending on which browser I'm on. This is what I see on Opera on my mobile:

but this is what I see on Safari on my iPad:

[arhadthedev]

When I opened this comment it showed the ghost mannequin icon, but as I was reading, it updated to the real profile image. So I guess it's a caching thing?

DevTools shows no attempts of afterload network activity. Its console also reports nothing but unrecognized feature: 'interest-cohort' and lazy loading of my own userpic.

It seems to vary depending on which browser I'm on

• desktop Edge 100.0.1185.36 I reported from shows the mannequin
• mobile Chrome 99.0.4844.88 for Android immediately shows a correct avatar

[arhadthedev]

@ezio-melotti Any news from the GitHub side? The issue continues to occasionally manifest itself.

[ezio-melotti]

I haven't heard from them.

[arhadthedev]

Is there an ability to contact the team once more? The pages mentioned in this issue continue to manifest the bug.

[ezio-melotti]

If the problem is in the issue metadata (i.e. the user/author/commenter is stored as a mannequin), it might be difficult (or impossible) to fix it. The only thing that comes to mind is trying to reclaim the mannequin for that user and see if it triggers an update that solves the problem, but that can only be done for org members and it needs to be done manually.

Since this doesn't seem easy to fix and doesn't seem to create any major issue, I think we can just close it.

[arhadthedev]

Since this doesn't seem easy to fix and doesn't seem to create any major issue, I think we can just close it.

In addition, this problem is transient and will stop to manifest itself after all migrated issues are closed.