Closed Nayelianne closed 1 year ago
Hey! Thanks for reporting, appreciate all the detail.
Since I was unsure if Leech was a special tag that only Anki itself was allowed to use, I changed the Leech tag to LeechT just in case. I almost thought I had it sorted out, but the same error eventually occurred regardless.
Oh yeah, very good point actually! Should probs mention that somewhere to be honest but, yep, "Leech" is pretty much reserved by Anki so you might run into issues using it like ya thought.
Either way, looks like a duplicate of #4. I posted a hot-fix version there if you wanna give it a try and see how that goes. Wish you the best! (https://drive.google.com/file/d/103Bio5kbizH7znIh1BiqF10uTHtHUgeK/view?usp=sharing)
Bug/Issue Description I'm getting the mysterious error below, it takes a while some times, it some times happens when I hit "Again" on a card, on others it's when I hit "Good" on different cardd.. It doesn't happen if I undo the review and repeat the action. so I'm unsure what's causing it. The one addon I thought could be conflicting is morphman, but it wasn't active on the deck I was reviewing.
To Reproduce Review things for a while, specific trigger yet unknown. I might try to deactivate most of my addons to see if I can narrow it down to a compatibility issue, but some times it takes a lot of cards for the error to happen, so it can prove time consuming for something that could potentially just be a unrelated bug. So I figured I'd register the issue here for starters.
Error Message
System/Debug Info
Additional Context These are my settings: On the Actions tab, I have an Add Tag active in the Leech Actions, and on Unleech I have it adding a tag and removing the previous Leech tag. From the Advanced tab I only have "Show options in Tools menu" active, and the default filled "Use a custom tag to keep track of toolkit updates across devices"
Since I was unsure if Leech was a special tag that only Anki itself was allowed to use, I changed the Leech tag to LeechT just in case. I almost thought I had it sorted out, but the same error eventually occurred regardless.