Since we updated to latest Phabricator version last week, I've noticed a couple of times that notifications refuse to mark themselves as "read" even after visiting the ticket or diff in question.
First few times this happened I manually cleared it with "mark all as read" which worked. I am certain that at least once this happened with a differential revision notification although I have no screen shots of those times.
Now it's come up twice more so thought I'd report it.
See: {F160802}
In this screen shot: you can see ticket 15392 appears twice in the list (with same timestamp/message). From the open tabs you can see that I have viewed it and I DID refresh notifications page afterwards.
The other unread one indicated in the badge is a totally different ticket which exhibits same behaviour - two identical entries in the notifications list one of which is marked as read and the other is not despite having reloaded both ticket and notifications page several times. The only difference is that in the other example further down the notification list. the one stuck as unread appears //before// the read one.
My wild guess is that the bug is that these tickets are causing double notifications for some reason and that the auto-mark-as-read functionality on view is only finding one of the records and marking that as read.
No one is online right now who can tell me exactly which version/commit we have deployed right now but it was updated to the head of master on Friday 23 May.
If you can think of any more info that might help debug please ask.
Thanks.