Page MenuHomePhabricator

getting bogus "No new message" occasionally
Closed, ResolvedPublic

Description

Accasionally, I get a "no new messages" kink in the personal tool bar even
though there certainly are new messages.

For instance, it says "18 new messages", I did not access or read any messages,
follow a link in another browser tab, the new tab says "no new messages" in the
personal toolbar, I follow yet another link, and the nwe page tells me "18 new
messages again.

From all I observed, I currently must assume this behaviour is new, and random.
I watch it hoping to get a better clue as to how to reproduce it. Up to now only
seen in translatewiki.net, but I did not have really many chances to observe it
elsewhere.


Version: unspecified
Severity: normal
Whiteboard: aklapper-moreinfo
URL: http://translatewiki.net/wiki/Special:NewMessages

Details

Reference
bz28579

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 11:29 PM
bzimport set Reference to bz28579.
bzimport added a subscriber: Unknown Object (MLST).

Another observation: I got "no new messages" following an external link in an e-mail sent by the wiki announcing a page edit by someone else. Immediately klicking the "no new messages" link on the diff page (that I got to from the link in the e-mail), I was shown "11 new messages", appears to be is correct.

Maybe this is one more case of bug 31251?

Using LQT daily and I haven't found this problem. Is it reproducible or at least seen nowadays?

Purodha: Is this still an issue nowadays?

(In reply to comment #3)

Maybe this is one more case of bug 31251?

There seems to be a common root problem at least: "My new messages" number requires an extra change of page in the browser to get updated. This leads to all kinds of combinations that will show a wrong number.

I would resolve as duplicate of 31251. If anybody disagrees then we can reopen.

  • This bug has been marked as a duplicate of bug 31251 ***

(In reply to comment #5)

Purodha: Is this still an issue nowadays?

It did not occur for a long time now (in translatewiki.net), so I tend to believe it has been solved.