Skip to main content
Meta Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

11
  • FYI, it doesn't provide very many details, including the OP yet confirming or denying my suspicion mentioned in my comment there (which also links to this question here), but due to the timing, I suspect that the Math meta post of Asking clarification between "presentation" of comments may also be due to this issue. However, it's currently closed as a duplicate, so you may potentially wish to just comment there. Commented Nov 12 at 3:06
  • 3
    @JohnOmielan Thank you for pointing me to the other post. I will comment there! Commented Nov 12 at 15:52
  • @ShiyaoLi Does this older report have the same cause? Commented Nov 12 at 18:07
  • 3
    @SonictheAnonymousHedgehog All inbox counter errors are caused by counting unread notifications incorrectly, though the specific reasons vary by case. In this instance, the incorrect count was caused by an error happened in the one-time batch-sending process. I’m not sure why comment notifications behave that way, but their underlying issue is different from this one. Commented Nov 12 at 18:31
  • 1
    @ShiyaoLi, but why just not guard counter to 0, so not show negative value? Commented Nov 12 at 20:26
  • 8
    @Grundy This is an older bug in the inbox system and eventually we'll need to do that. Commented Nov 12 at 20:48
  • @ShiyaoLi, btw, why when i "mark as read" concrete notification in inbox - counter reset to 0, but on refresh still show regative value? seems like on client added some "hotfix" but not update server state Commented Nov 12 at 22:06
  • 2
    @Grundy I haven’t personally worked on the inbox system, so I don’t want to risk providing inaccurate information. I may not be very helpful beyond identifying what happened with the room guidelines notifications. Sorry about that! Commented Nov 12 at 23:07
  • @ShiyaoLi oookay :) Commented Nov 13 at 0:19
  • Re "It affected some users who own multiple chat rooms", I don't think I own any, and it affected me. But "Mark all as read" did fix the issue. Commented Nov 13 at 19:26
  • 3
    @ikegami You own 3 long-deleted rooms. Based on other reports, it seems the script did not properly ignore those somehow. Commented Nov 13 at 19:40