25

Since earlier today, the red badge to notify me of new inbox items vanishes when reloading the page or opening another SE page in a new tab (not opening the inbox in either tab). Can this new behaviour somehow be switched off again?

When opening the inbox, the new items are still highlighted, just the red badge is missing. Accessing the unread inbox via the api (https://api.stackexchange.com/docs/inbox-unread) will also still include these items.

(the green badge from rep notifications is not affected , this one stays put even when reloading the page)

OS: macOS 11.6.8

Browser: Firefox ESR 102.3

Improve this question
20
  • 4
    I also noticed this last night (on Chrome; Windows). Likely related to Inbox improvements: marking notifications as read/unread, and a filtered inbox view.
    – 41686d6564
    Commented Oct 13, 2022 at 11:12
  • @41686d6564standsw.Palestine Yes, might be related. Still annoying if the notification silently vanishes without opening the inbox.
    – samcarter_is_at_topanswers.xyz
    Commented Oct 13, 2022 at 11:15
  • 2
    Yeah, it's definitely a bug. Actually, it just happened again with the notification about your reply.
    – 41686d6564
    Commented Oct 13, 2022 at 11:16
  • I only saw your first comment because I simultaneously got an upvote and wanted to edit the question to say that the rep badge is not effected :P
    – samcarter_is_at_topanswers.xyz
    Commented Oct 13, 2022 at 11:19
  • 8
    We're checking into what might be up here. Thanks for the report.
    – Catija Staff
    Commented Oct 13, 2022 at 13:17
  • 3
    @41686d6564standsw.Palestine Those referenced inbox improvements haven't been released yet. That being said, we have someone looking into this bug here shortly.
    – Tyler McEntee Mod
    Commented Oct 13, 2022 at 13:23
  • 4
    If it helps i.imgur.com/33xE3nx.gif I THINK this shows the bug.
    – Journeyman Geek Mod
    Commented Oct 13, 2022 at 13:25
  • 3
    Not sure if it's related but I'm noticing that chat notifications aren't coming as quickly as they should. I usually see them in my inbox within a minute but they're taking more like 10-15, which makes me feel like it's not considering the chat preference for "quicker notifications".
    – Catija Staff
    Commented Oct 13, 2022 at 13:29
  • 2
    @Barmar - nope, my notifications are still only showing up on chat.
    – Mithical
    Commented Oct 13, 2022 at 17:40
  • 1
    @Barmar Still experiencing the problem
    – samcarter_is_at_topanswers.xyz
    Commented Oct 13, 2022 at 18:04
  • 1
    Same, I got back to the site after few days away, there were four new items, no red number at all, I clicked anyway just to check, and saw the new items. My guess, partial publishing of the new inbox, maybe done for testing, causing some issues.
    – Shadow Wizard
    Commented Oct 13, 2022 at 20:54
  • 1
    @ShadowTheKidWizard My theory is that the code for the new inbox was safely stored in a closed box, but now that we get closer to Halloween, the code staged an escape last night when nobody was looking and now everybody at headquarters is running around trying to catch all the escaped code lines -- might not be the most accurate theory, but fun to imagine :P
    – samcarter_is_at_topanswers.xyz
    Commented Oct 13, 2022 at 21:04
  • 4
    We've identified the issue and prepared a PR for it. We'll work on getting it reviewed and built out in the morning. Thanks for your patience.
    – Catija Staff
    Commented Oct 14, 2022 at 1:20
  • 6
    @ShadowTheKidWizard Yep! There'll be an update soon but I've changed the tag for the time being. :)
    – Catija Staff
    Commented Oct 14, 2022 at 13:50
  • 1
    @Catija Thank you and the devs for fixing this!
    – samcarter_is_at_topanswers.xyz
    Commented Oct 14, 2022 at 13:51

1 Answer 1

Reset to default
8

As reported, this got fixed and deployed this morning. Here's a fun spot the difference:

Current.GlobalCache.GetInt(key)
Current.GlobalCache.GetAsync<int>(key)

Turns out, GetInt actually returns a long - go figure.

Thanks for your patience and the report, and also way more interesting inbox features to follow

Improve this answer
7
  • 5
    I bet that took a long time to figure out
    – Kyle Pollard StaffMod
    Commented Oct 14, 2022 at 17:27
  • OMG, just now realized there are two different @Kyle's here! :-D
    – Shadow Wizard
    Commented Oct 14, 2022 at 17:28
  • So, to solve the riddle, you had to change to Current.GlobalCache.GetAsync<long>(key) in order to fix the bug?
    – Shadow Wizard
    Commented Oct 14, 2022 at 17:29
  • 1
    Don't forget to cast that back into an int (int)(await Current.GlobalCache.GetAsync<long>(key))!!
    – KyleMit StaffMod
    Commented Oct 14, 2022 at 17:31
  • 6
    Nobody better have more than 2147483647 inbox notifications, or the whole thing falls apart
    – KyleMit StaffMod
    Commented Oct 14, 2022 at 17:32
  • 2
    @ShadowTheKidWizard, We're informally known as kyle-east and kyle-west
    – KyleMit StaffMod
    Commented Oct 14, 2022 at 17:32
  • 1
    @Kyle haha! But who is which, and why? :-)
    – Shadow Wizard
    Commented Oct 15, 2022 at 7:00

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .