Sorry if this isn’t the correct place to do this - the GitHub directed me here but didn’t tell me what category to use.
Will you go to Help (or Anki) > About – click Copy Debug Info – and paste that full result here?
This sounds like a prior issue that should have been fixed in 24.06. Can you click on the bar in that 3mo graph and the bar in the all graph and see if you can find whether that card is due on 53 or after 53?
1 Like
Anki 25.02 (038d85b1)
Python 3.9.18 Qt 6.6.2 PyQt 6.6.1
Platform: Linux-6.13.2-x86_64-with-glibc2.40
Is it possible that it’s happening because I switched to 25.02, then launched it once in 24.06, before going back to 25.02?
As of now, the latest card is “56 days”, but the same behavior is occurring. When I click on the card itself, it says Due 2025-05-28, which, assuming 2025-04-03 is “1 day”, would be 56 days.
My question was about clicking on the bar in the graph to see what search string you get, and see if it correctly shows you the furthest card. But it sounds like you’re seeing something different.
But is it working correctly now? If it’s showing you the furthest card on “56 days” and that card is actually due on that day – that sounds correct.
Thanks! Let’s see if anyone can reproduce it in 25.02.
For the first time I am not seeing this bug in one of my decks. The final section is “240-243 days”, and it accurately shows 1 card in that group. Perhaps this glitch will only happen when all your cards have short intervals?
Never mind, it’s back to not working
“0 cards due between 270-275”
There is one card due at 275 days. Maybe if it was due in 270-274 days it wouldn’t break.
Can you go to the browser and export a single card (without media) that has this problem? Maybe someone here can reproduce it with your card if you share it, which then might lead to a fix.
For similar issues in the past, it wasn’t a particular card that mattered – it had to do with the cards on the furthest due date in the future and how the cards were divided into bands.
It looks like I’m able to reproduce this on 25.02 (Windows 11, with add-ons disabled) – but only for 1mo, 3mo, and 1yr. In each instance, it’s the cards that are due on the last day of the band that are not being counted.
The “all” graph is just fine for me, but notably, there is only 1 card due in that band.
The issue seems related to the labelling of the graphs. For 1mo and 3mo, each band is a single day, but then for some reason the final band is 2 days – and leaves off the final day’s cards from the tally. Similarly for 1yr, each band is 5 days, but then the final band is 6 days – and leaves off the final day’s cards from the tally. [The “including day 31 in the band, but not counting its cards” aspect of this sounds very familiar to me, but I haven’t found where it was reported yet.]
Because of that, I can see how the visibility of the issue comes-and-goes on the “all” graph, depending on where in the final band the final card is due.
2 Likes
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.