Page MenuHomePhabricator

Timestamp discrepancy for cross-wiki notifications
Closed, ResolvedPublic

Description

Hi. Is it normal - two absolutely different timestamps for the same notification? Thank you.

Screenshot_2016-07-17-00-56-52.png (600×1 px, 140 KB)

Event Timeline

@IKhitron - no it should not. The cross-wiki bundle (when the bundle is not expanded) the timestamp should be the most recent one.
Did you mark as read some of the notifications in the cross-wiki bundle and then the bundle timestamp became different or a new message has come when you were on the page? Anyway, I will be checking couple of scenarios to see where that discrepancy may come from.

I wonder if this might be a bug in the transition flag code, but I'll wait to see if Elena can find reproduction steps for this.

Mattflaschen-WMF renamed this task from It should be like that? to Timestamp discrepancy for cross-wiki notifications.Jul 18 2016, 5:23 PM

I saw on my local wiki two cross-wiki notifications in bundle. Did not pay attention on timestamps. I clicked on the blue dot on one of them. it disappeared, and this is the result.

I saw on my local wiki two cross-wiki notifications in bundle. Did not pay attention on timestamps. I clicked on the blue dot on one of them. it disappeared, and this is the result.

If you reload the page, does the bug persist?

I have no idea. I closed it yesterday.

Generally, the problem is - the timestamps are not promptly, i.e. automatically updated.
Case 1: bundle timestamp > most recent timestamp of any of the notifications

Screen Shot 2016-07-18 at 1.52.34 PM.png (327×637 px, 45 KB)

Case 2: bundle timestamp < most recent timestamp of any of the notifications
The steps to reproduce the issue are

  1. When user A is logged in, user B sends user A a cross-wiki notice/alert.
  2. User A without refreshing the page, opens the flyout. Several things happen
  3. if necessary, the name of foreign wiki gets added to the list of foreign wiki bundle list
  4. the cross-wiki bundle timestamp gets updated to the timestamp of the most recently received notifications
  5. when the cross-wiki bundle is expanded, there is a mismatch between cross-wiki bundle timestamp and the most recent timestamp of the bundled notifications.

So, user A sees that the bundle timestamp is earlier than any timestamp of any notifications in the bundle.

Screen Shot 2016-07-18 at 1.36.50 PM.png (189×575 px, 27 KB)

Screen Shot 2016-07-18 at 1.37.01 PM.png (382×573 px, 55 KB)

@IKhitron I agree that the issue should be closed. There were some backend improvements that made timestamps more responsive to updates.

I could not reproduce the case of bundle timestamp > most recent timestamp of any of the notifications

The case of bundle timestamp < most recent timestamp of any of the notifications is still relatively easy to reproduce but only for some edge cases as described in my Case 2).

Screen Shot 2017-04-11 at 12.44.37 PM.png (463×561 px, 66 KB)

Etonkovidova triaged this task as Lowest priority.