This is due to a problem with re-caching. It is seeing the new friendship activity on both users' activity streams and then re-caching both of them.
There needs to be a flag in the code that checks to see if one side of the friendship request activity has already been cached in the site-wide stream. This happens when initially recording it, but not re-caching, which is why it doesn't duplicate straight away.
Re-caching may actually no longer be needed due to the cache now being dynamically updated. This would fix the problem, and will be looked in to.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
This is due to a problem with re-caching. It is seeing the new friendship activity on both users' activity streams and then re-caching both of them.
There needs to be a flag in the code that checks to see if one side of the friendship request activity has already been cached in the site-wide stream. This happens when initially recording it, but not re-caching, which is why it doesn't duplicate straight away.
Re-caching may actually no longer be needed due to the cache now being dynamically updated. This would fix the problem, and will be looked in to.