9

This screenshot: enter image description here

shows that there are 1871 pages when you click the 1870th page, which has exactly 50 items in it, but the 1871st is empty. Why is there a 1871st page if it isn't needed?

EDIT:

This behavior is only present sometimes. It took a minute to reproduce this more than three times, because of the number of items coming in and out of the list.

5
  • It probably generates a new page if the last page is full, without checking to see if any would actually be added to that new page. – Sonic the Curiouser Hedgehog Sep 12 '20 at 19:03
  • 1
    Combination of queries done as the state changes & caching. Like most concurrent system specified and/or implemented behaviour. – philipxy Sep 12 '20 at 19:03
  • 3
    Same bug as this one - it happens only when the last page has the page size amount of items, in your case 50. Now since two more questions were asked after yours, the bug doesn't "happen", but it's not caching - when there will be 50 exactly in the last page, a "zombie page" will appear and be empty when clicked. – Shadow The Vaccinated Wizard Sep 12 '20 at 20:47
  • 1
    Maybe there were two questions on the 1871st page but then the system deleted two questions leaving a blank page. – Mari-Lou A Sep 14 '20 at 15:42
  • @Mari-LouA even so, it shouldn't leave a "zombie" empty page. – Ollie Sep 14 '20 at 19:29
3

As you note, this is an intermittent issue, and I wasn't able to reproduce it.

Additionally, based on our current roadmap, this isn't work that we will take on, as it doesn't coincide with functional areas that we plan to improve in the near future. We recognize that time and thought was put into this request, but unfortunately, we can't prioritize it at this time.

6
  • I disagree. This can be reproduced when the last page has exactly 50 questions (when page size is 50), then there appears "extra" page which is blank when clicked. I also said that here. I do accept a decision to reject the bug based on the new canonical "not in our roadmap", but in such case tag should be changed to status-declined. – Shadow The Vaccinated Wizard Feb 20 at 17:13
  • @ShadowWizardisVaccinating I implemented a few paginations in C# ASP.NET and this is a lot more difficult than it may seem. If you check Google main page the pagination is often also broken :P – bad_coder Feb 20 at 19:07
  • @bad_coder never said it was easy to fix. Just possible to reproduce. And yeah, got into lots of trouble implementing pagination as well. ;) – Shadow The Vaccinated Wizard Feb 20 at 21:18
  • I didn't say it was impossible to reproduce, @ShadowWizardisVaccinating, I said I wasn't able to reproduce it since the issue occurs intermittently... but I guess you disagree with the fact that I wasn't able to reproduce it...? I'll change the tag, if that's the cause for contention here ;) – JNat Feb 22 at 10:14
  • @JNat yes, the status-norepro tag is "final" and means no further attempts to fix it will be made since it's not possible (for the developers who should fix it) to reproduce the problem. Declined is also final, but fits better here. Thanks! – Shadow The Vaccinated Wizard Feb 22 at 10:27
  • @ShadowWizardisVaccinating regarding their new stance on status-declined it's no longer final but should be interpreted as "status-declined-for-now" – Luuklag Feb 22 at 10:40

You must log in to answer this question.

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