It seems to have gone half-through, i.e. in the same comment:

PleaseStand added a comment.Via Conduit · Jul 28 2006, 2:43 AM

Invitatious wrote:

Do you have now one Phabricator account with several email addresses (recommended) or different Phabricator accounts for each email address?

In T75818#783460, @Qgil wrote:

It seems to have gone half-through, i.e. in the same comment:

That was only after I removed and re-added the "Invitatious" (capitalized) email address as I described (and waited for the hourly cron job to run). I added the "invitatious" (lowercase) address within a day of creating my Phabricator account (on October 22). Unless there was some bug involving multiple email addresses that was fixed since the scripts were first run, case sensitivity would probably explain the problem I was having.

The "half-through" part (only comment metadata updated, not comment text, description text, or task metadata) may be a different bug. I think I already saw that happen for at least one other user's comment on some other task, though I don't remember which one.

Do you have now one Phabricator account with several email addresses (recommended) or different Phabricator accounts for each email address?

A single account, which I created using my LDAP credentials. Then I linked my MediaWiki.org account to that account. Then I added the "invitatious" (now "Invitatious") email address (and did not make it the primary address).

A few notes for troubleshooting these issues.

The case of "user comment is attributed but foo wrote: remains is what happens when viewing a comment that has been fixed but the remarkup cache has not yet been cleared. It is not performance friendly to clear this cache often so we only do it after batches and not individual users.

I haven't verified, but yes I do believe the email comparisons are case sensitive, but only if someone used case in the original system. We could look at changing it but it hasn't been a problem thus far.

I'm not sure where the idea that this job is run hourly came from. That is not the case at this time.

Yes, header data (author/cc/assignee) is a separate thing from comment metadata so them not being updated at exactly the same time is expected.

If I understand correctly this has all caught up, it was only a matter of waiting.

In T75818#783730, @chasemp wrote:

I'm not sure where the idea that this job is run hourly came from. That is not the case at this time.

Ah, I see that since I had last checked, two of the three cron jobs were changed to run daily instead of hourly.