Thread

1. apocalyptic0n3 · 1789585905 · focus · HN ↗

   Calling this "severe" feels overblown. It's a UI mismatch likely caused by using multiple caches that are out of sync. I feel like every engineer on this site has encountered this exact bug at one point or another. It's an easy one to run into, especially in bigger orgs.

   1. layer8 · 1789586174 · focus · HN ↗

      The second screenshot with “1 3 Next” seems pretty hard to justify.

      Taking care that such incongruent representations can’t happen even in the face of inconsistent backend caches is part of proper UI state management.

   2. thibaut_barrere · 1789586183 · focus · HN ↗

      Yes but in the case of GH, it also happens in cases where the data is old: not just a temporary drift.
   3. queenkjuul · 1789613963 · focus · HN ↗

      The "page two is inaccessible" thing is, imo, severe. I've seen it myself at work, and there are lots of parts of the UI where I'm regularly looking for something on page 2. I didn't even think to try the JavaScript console hack but like, i (my employer) is paying for access to that data, and it's simply not there...

Unofficial Hacker News client; not affiliated with Y Combinator.