Closed wheelson93 closed 4 years ago
Same here, the problem began when I suspended some card with "Trigger and actions: change one card depending on what occurs on another card" addon. If I exclude that deck the color comes back. Hope this helps to identify the source of this problem.
It randomly started working again last week. No idea why, but I'm not complaining.
On Mon, May 11, 2020, 4:30 PM cocowash notifications@github.com wrote:
Same here, the problem began when I suspended some card with "Trigger and actions: change one card depending on what occurs on another card" addon. If I exclude that deck the color comes back. Hope this helps to identify the source of this problem.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/glutanimate/review-heatmap/issues/70#issuecomment-627000184, or unsubscribe https://github.com/notifications/unsubscribe-auth/APHWSGCXBFHGTSRQ5JCZJPDRRB377ANCNFSM4MLOM7VA .
It randomly started working again last week. No idea why, but I'm not complaining. … On Mon, May 11, 2020, 4:30 PM cocowash @.***> wrote: Same here, the problem began when I suspended some card with "Trigger and actions: change one card depending on what occurs on another card" addon. If I exclude that deck the color comes back. Hope this helps to identify the source of this problem. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#70 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APHWSGCXBFHGTSRQ5JCZJPDRRB377ANCNFSM4MLOM7VA .
Do you recognize what was the source of your problem or the bug just went away randomly?
Well for the record mine got fixed too after making a filtered deck that contained all the cards from the "bugged" deck that was avoiding the addon to work properly. I'm not sure why it works so take my comment with its necessary dose of skepticism.
Thanks for the reports, guys. Hmm, this is a weird one. First time I'm seeing an issue like this since the add-on was published. I haven't been able to reproduce the problem on my end, so I assume it must be something particular about your guys' setups that's triggering this (add-ons, decks, etc.).
A couple of things that might help me get to the bottom of things:
@cocowash: Do you happen to still have those cards / that deck handy that you found to be factoring in somehow? If so, it would be super helpful if you could send it to me as an .apkg
export.
To do so, you can just click on the gear icon next to its name in Anki's main screen, and then select "Export". A dialog should pop up that allows you to select the export format and customize some other settings. As the export format please select "apkg", and as for the settings: Please check the option to include scheduling and uncheck the option to include media.
Once you have the exported deck handy, it would be great if you could send it to per email via ankiglutanimate@gmail.com
Thanks a lot in advance!
I was able to reproduce this bug and sent the email containing the bugged deck. Version 2.1.24 (359b9f5c). I was able to narrow it down to 1 card: Front: "con-tendere"; Back: "eilen/ kämpfen/ sich bemühen". With this card active, I am getting the same issue: The heat map no longer lights up when I start Anki. However if I click on the boxes of review heat map, (days) the colours appear.
Thanks for the detailed bug reports and sample decks, guys. I think I was able to track down the issue here:
@cocowash and @hhkbprojp
Both of your decks contain cards whose scheduling somehow got corrupted. E.g., in the case of your deck, @hhkbprojp, the due date looks as follows:
That is, Anki thinks the card will become due sometime in the year 4340593. I found the same issue with one of your cards, @cocowash . To be fair, there is a small chance that Anki's algorithm is being prophetic here and that humanity will discover the secret to eternal life in our our lifetime. In a much more real way though, the cards likely got messed up by a third-party add-on and/or a bug in Anki's scheduler.
@cocowash, given that you remember the issue occurring after using "Trigger and actions: change one card depending on what occurs on another card", that might be one possible cause. However, reading through @wheelson93's initial bug report, it doesn't seem like he was using this add-on, and I'm not sure if you, @hhkbprojp, were using it, either.
In any case, coming back to Review Heatmap: I've implemented a workaround in c758478125b60a81c66c87c35b12b7968ec0a348 that simply ignores invalid due dates. This should make your guys' heatmaps work again, even in the affected decks.
I've attached a ready-made build of Review Heatmap using that change below. It's formatted as a zip because GitHub does not support uploading .ankiaddon files in comments. To install it, just rename the .zip ending to .ankiaddon and follow along with the usual installation steps. Please let me know if this works for you and I'll go ahead with updating the main download.
review-heatmap-v1.0.0-beta.1-4-gc758478-anki21.zip
Important: I highly suggest that you guys try to track down what caused this corruption in your scheduling. It's important to nip this in the bud early on, so that other cards don't get corrupted as well.
@Arthur-Milchior Pinging you here since "Trigger and actions: change one card depending on what occurs on another card" came up. Are you aware of any scheduling issues that could cause these invalid due dates?
Ah, it seems like running a database check thankfully fixes the incorrect due dates. So yeah, head to Tools → Check Database, and Anki should inform you that it found a number of cards with invalid due dates and fixed them. This still won't prevent other cards from being affected in the future (if the underlying cause is still at play), but it's good to know that your cards can at least be somewhat recovered in this manner.
Thanks for the response, currently my largest due date is settled to (2021/03/14) so maybe as you said it was a problem concerning scheduling that got bugged on my anki and then it got automatically fixed. Even though, if I check the database it says that I have 229 with errors. I can't find those cards even if I unsuspend all my cards the largest due date remains the same.
Since May, I could not replicate the same error, and I constantly use the addon of Trigger and actions and also Morphman, so I'm not sure what was the origin of the bug in the first time. I know that morphman re-schedule new cards in a way that you see easier cards depending on certain parameters, but It doesn't touch young or mature cards.
Nzver heard of. But its not a widely used addons.
However it does not change scheduling, only queues, so i'd be surprised
Thanks so much!
Ah, it seems like running a database check thankfully fixes the incorrect due dates. So yeah, head to Tools → Check Database, and Anki should inform you that it found a number of cards with invalid due dates and fixed them. This still won't prevent other cards from being affected in the future (if the underlying cause is still at play)
I just wanted to mention that I just had the same issue. I dont use any addons other than the heat map. I checked my notes and also had a card due in the year 4340593. I did the "Check Database" and it fixed everything but I suspect the bug is still somewhere in Anki itself.
@ElectricPaul Glad to hear that! Thanks for letting me know.
Closing this issue report as the issue should be fixed on the add-on's side.
Thanks for the detailed bug reports and sample decks, guys. I think I was able to track down the issue here:
@cocowash and @hhkbprojp
Both of your decks contain cards whose scheduling somehow got corrupted. E.g., in the case of your deck, @hhkbprojp, the due date looks as follows:
That is, Anki thinks the card will become due sometime in the year 4340593. I found the same issue with one of your cards, @cocowash . To be fair, there is a small chance that Anki's algorithm is being prophetic here and that humanity will discover the secret to eternal life in our our lifetime. In a much more real way though, the cards likely got messed up by a third-party add-on and/or a bug in Anki's scheduler.
@cocowash, given that you remember the issue occurring after using "Trigger and actions: change one card depending on what occurs on another card", that might be one possible cause. However, reading through @wheelson93's initial bug report, it doesn't seem like he was using this add-on, and I'm not sure if you, @hhkbprojp, were using it, either.
In any case, coming back to Review Heatmap: I've implemented a workaround in c758478 that simply ignores invalid due dates. This should make your guys' heatmaps work again, even in the affected decks.
I've attached a ready-made build of Review Heatmap using that change below. It's formatted as a zip because GitHub does not support uploading .ankiaddon files in comments. To install it, just rename the .zip ending to .ankiaddon and follow along with the usual installation steps. Please let me know if this works for you and I'll go ahead with updating the main download.
review-heatmap-v1.0.0-beta.1-4-gc758478-anki21.zip
Important: I highly suggest that you guys try to track down what caused this corruption in your scheduling. It's important to nip this in the bud early on, so that other cards don't get corrupted as well.
Seems I had the same problem. One card did not have any due time. I have 2 addons that may have caused this. or anki itself as mentioned above. One that auto adjusts ease factor based on performance and one that auto buries cards I type again very often in a day. Thankfully it was just one card and after resetting it it got fixed. Will try "cheking database" if happens again. Thanks for the help!
Problem description
Please describe the issue concisely in here. In case of an error: Walk us through the steps you took to get there. What happened? What did you expect to happen? No error is being tripped. The add on works completely other than the boxes aren't being filled in with colors. They all appear gray, but I can hover over it and it will give me details of the cards done on that date and the forecast.
Checklist
Please replace the space inside the brackets with an x if the following items apply:
Information about your Anki set-up
Please fill out the section corresponding with your Anki version:
2.1.22
If you are using Anki 2.1
Please open Anki, go to Help → About, click on "Copy Debug Info", and paste the result between the backticks below (if the button does not appear you are using an older version of Anki 2.1 and will need to update first):
If you are using Anki 2.0
ONLY IF YOU ARE USING ANKI 2.0: Please open Anki, go to Help → About, find the two lines starting with
Version:
andQt
, and copy-paste them between the backticks below:Please fill in details about your operating system (Windows/macOS/Linux, which version):
Please open Anki, go to Tools → Add-ons, take a screenshot of your installed add-ons, and paste it below:
Error message (if any)
If you've received an error message, please copy and paste it between the backticks below: