#Problem with running Recalc with AnkiMorphs

7 messages · Page 1 of 1 (latest)

nocturne current
#

I came back from a 3 week vacation today, when I opened Anki and updated some addons, I started not being able to run recalc with AnkiMorphs.

I've narrowed the problem down to a specific note type causing the issue, but I can't progress any further than this. I've also updated anki to the latest version, but it hasn't fixed it. I'm not sure what else to do, any ideas?

The note type is Migaku's Japanese Sentence Note type.

The error I get when running Recal is the following: (apparently it posts the info log as an attatchment, probably because of the size)

spiral ferry
#

I'm going to do something very bad and just give you the output from ChatGPT. I've used ChatGPT to debug error messages before, and it's generally helpful. The answer here seems reasonable, but I haven't tested any of what it suggests to do.

Follow at your own risk.

⚠️ ⚠️ Make sure to back up your collection first. ⚠️ ⚠️

https://chatgpt.com/share/6903c956-c044-8006-8167-30606433e168

I did test enough to realize that it's a little off on two points: (1) to open the debug console, do this and (2) to see the output of any command you run in the debug console, you'll need to wrap it in print()

#

--
Obligatory, I don't know anything about Migaku or Migaku's Japanese Sentence Note type. So, even if ChatGPT is right about certain fields being filled with invalid JSON, I don't know what will happen if you delete the invalid JSON.

I also don't even know if ChatGPT is right about it being generally safe in Anki to blow away the data field.

🤷‍♂️

nocturne current
#

I ran the problem through chat gpt as well, it gave be a bunch of different steps and suggestions. I did some of them, it didn't work. Others were a bit blatanly wrong, but that happens

#

I'll read and run through this fix however, it seems different than what it suggested the problem was the other times, let me see if it works

nocturne current
#

Interesting, looks like I finally got it fixed! I was able to run the calc, I don't know if I did any real damage to the cards, but I'll have to check that out later, it's late and I need to go

#

At least at first glance, it looks like it worked, ty!