Oh yeah, that’s definitely not right! Not sure why it’d be doing that. Are you familiar with using the Firefox debugging tools? The script doesn’t output a lot of information, but there might be something in the console logs.
I’m going to give this a try, thanks. I have way too many leeches, it’s so frustrating.
I’m not really getting any errors. Just the uncaught expection.
But after this result I’m still getting the same amount of leeches
I’m not sure if that uncaught exception is coming from the leech trainer or the progress script below it. If you disable other user scripts and just have the leech trainer does it start working? There could be interference, I guess, but I would have thought that was unlikely.
I’ve turned off all other scripts (expect Open Framework) and it still doesn’t work. get the uncaught exception again. It appeared when I started and appeared when I finished and doesn’t update.
It does update sometimes, as the number changes, but probably when I close the browser at the end of the day and restart it in the morning (it’s my work PC). I’ll check that tomorrow
New day at work, restart of the browser and the amount of leeches changed (From 59 yesterday to 46 tomorrow). A hard refresh (F5) or reopening WaniKani doesn’t do this, only a restart of the browser.
Okay, that’s bizarre. Firefox on which OS? I’ll see if I can recreate it.
The script doesn’t lower the leech count… is there a fix available? Here is my console log
This one I’ve normally seen be sorted with a restart of the server, which I’ve just done. I’m going to try and get to grips with Go, the language it’s written in, a bit more and add some more logging. That way I’ll hopefully learn some more about what’s causing these errors.
Step one of being able to debug and extend the leech server has been deployed.
For the technically minded that meant getting a bit more to grips with go, upgrading packages, the core language version, containerising, and swearing.
For everyone, it means please let me know if it all stops working catastrophically.
Edit: Yeah, it’s borked. On it.
Edit 2: Yaaas! Showed it who’s boss. Turns out if you add a Procfile to a heroku app, but forget a web
dyno, then go back and add one in, you need to manually scale it up to 1 dyno or it’ll just ignore that part of the procfile. Anyway, bed time.
Still not lowering leech count for me
I am delighted and apprehensive to say…try it now, please.
Good job, now it’s working perfectly. Thank you!
Just posted an update so that the script will still be usable when the new dashboard rolls out. The link will now be in the top right corner, next to your account link.
Is it still possible to see the number of leeches you have in the review queue?
Yup, it’ll be back. First step is to make it look like the nice rollover effect on the new dashboard, then provide a breakdown of which levels your leeches are on.
Okay thanks! That sounds really cool, looking forward to it!
Stage one of updates complete, you should see an update rolling out.
Is anyone else currently having issues? I keep doing a training session but my number of leeches never decreases and so I’ve repeated the same exact reviews about four times.
None of my ad blockers are activated and I already expired, reset and updated my API V2 key. Any idea what’s happening or how I can troubleshoot further? Running the most recent version of Firefox 78.0.1 on macOS Mojave. Thanks!
Have you tried uninstalling and reinstalling the script? I am not sure this will help but this is something to try.