Bugged Review History

[sdavis175]

Tested on latest Anki version: Version ⁨24.04.1 (ccd9ca1a)⁩ Python 3.9.18 Qt 6.6.2 PyQt 6.6.1
File used: yaku.json
Tested with FSRS turned on and off (neither worked).

Review date in Anki does not match the review date from JPDB:

Notably, this error continues to show up in the console:

File "<string>", line 1, in <module>
  File "aqt", line 519, in run
  File "aqt", line 733, in _run
  File "C:\Users\ruuna\AppData\Roaming\Anki2\addons21\541896873\__init__.py", line 30, in import_jpdb
    stats = imp.run()
  File "C:\Users\ruuna\AppData\Roaming\Anki2\addons21\541896873\importer.py", line 136, in run
    'notes_created': self.create_notes(vocabulary),
  File "C:\Users\ruuna\AppData\Roaming\Anki2\addons21\541896873\importer.py", line 126, in create_notes
    self.backfill(note, vocab)
  File "C:\Users\ruuna\AppData\Roaming\Anki2\addons21\541896873\importer.py", line 102, in backfill
    self.backfill_reviews(jp_en_card, vocab.jp_en_reviews)
  File "C:\Users\ruuna\AppData\Roaming\Anki2\addons21\541896873\importer.py", line 69, in backfill_reviews
    current_state, new_state = self.card_state_current_next(card, rating)
  File "C:\Users\ruuna\AppData\Roaming\Anki2\addons21\541896873\importer.py", line 49, in card_state_current_next
    states = self.anki.col.backend.get_scheduling_states(card.id)
  File "anki.collection", line 170, in backend

Accessing the backend directly will break in the future. Please use the public methods on Collection instead.

I have a feeling it relates to this error: https://forums.ankiweb.net/t/answering-a-card-programmatically/24075/3
However, I have not been able to successfully implement the filtered deck solution from that post.

[llvtt]

@sdavis175 Thanks for reporting. I'll take a look into this in the next couple days!

[llvtt]

@sdavis175 I know it's been awhile on this issue, but I'm interested in starting development work on this plugin again. In case you still happen to be using JPDB and might be interested in using this plugin, would you mind sending me your downloaded reviews.json from JPDB? I've tried using my own but haven't been able to reproduce this issue so far.

[Gaine]

@llvtt Are you still interested in developing this plugin? I could send you my reviews.json, I had a similar issue where the reviews were mostly clustered on the date of import (except one, being the latest one I had done). Another odd thing is the oldest reviews after importing where cut off exactly at 31 days in the past (so imported today, but reviews history only exists per 14th of April). That doesn't seem like a coincidence!

[Gaine]

@llvtt After some testing, it seems at least my issue was caused by orphaned revlog entries. I had tried to upload my reviews previously, which might've been around the 14th of April! So every review I had uploaded at that time got messed up, and only the new ones showed up properly (probably). Running below code in the console fixes the issue, I don't know if it can be filtered to just these jpdb imports or something to not mess with people's other decks (I don't know enough about Anki to know whether this could even cause issues) and then integrated into the add-on.

import aqt
mw = aqt.mw
col = mw.col

# Delete orphaned revlog entries
col.db.execute("""
    DELETE FROM revlog
    WHERE cid NOT IN (SELECT id FROM cards)
""")

[llvtt]

@Gaine If you don't mind, I'd like to take a look at your reviews.json to see if I can reproduce the issues you're hitting. I am interested in making this plugin more stable for more people if possible. Thanks for all the digging you've done so far!

[Gaine]

@llvtt, I don't think there was anything special about my reviews.json file, seems to be more on the Anki side (for reference, I was using the latest version) with these orphaned entries. I even pruned it to just one item that I messed with a bit, and can consistently replicate this by uploading the file once, deleting the item, then uploading again. First upload is fine, any additional uploads produce wrong review dates unless I clear the orphaned entries. I have attached the small .json file I used for testing below.

reviews(1).json