For whatever it’s worth, this was a quite common complaint I heard about 1x1 on Reorder Ultimate 2. I never thought to suggest hitting the Force Reorder button, though. (I personally didn’t mind it staying on the same question until you get it right, but I also didn’t use the Item Info.)
Hmm, new console errors. They appear every time I submit an answer in self-study extra study mode. All seems to be working though, so maybe not important?
I’ll look into it
So when I use Reorder Omega to do my lessons, once I get to the lesson screen it freezes and goes into an infinite loop. I have to turn it off so I can do my lessons, or do them on my phone. Not sure why this happens.
I have some other scripts, so it might be related to that, but the lessons work once I turn off Reorder Omega.
Based on the console, I thought it might be related to the User Synonyms script? But this is what it looks like once Reorder Omega is turned off. Same commands, but it works this time
That’s interesting. I’ll likely be tied up for a couple of days more before I get back to scripting, but I will look into it
You could try disabling/uninstalling Lesson User Synonyms 2 and installing Lesson User Synonyms 3 instead and check if the problem still occurs.
I’m sorry, but I haven’t been able to reproduce this issue. I saw that error a couple of times during the development of the script, however it was always in Self-Study and due to something that I don’t do for regular reviews. I am a bit at a loss for what could be causing this. I think that honeybadger error is a red herring. If you look at the network tab in the developer tools (a tab just like console) when you submit an answer, do either of the (two) requests sent out take a long time to come back?
I’m not sure if it would (or could) cause any issues, but do you have compatibility mode enabled? (it is not needed for this script)
Nope, compatibility mode not enabled.
The issue obviously decided it doesn’t want to happen right now just when I need it to! But I’ll keep the network tab open for the next few days to catch it when it does and will let you know. I am consistently getting this error on every submit, but it doesn’t seem to be causing issues so probably irrelevant?
Thanks for all your effort!
Yeah, that’s just due to Self-Study being a hack, shouldn’t be an issue
Did you end up trying Sinyaven’s advice?
Do you still have script compatibility mode enabled? I have noticed that having it enabled causes that to misbehave. I suspect a race condition. Although unless you need compatibility mode on you might just have to turn it off to fix it.
These are still there for me. What browser are you on?
Nope, both seem to be fast even when having the issue - they’re sent out on the first enter press and take only a few hundred ms, and after that I still have to press enter multiple times more before it finally continues onto the next item.
(Screenshot of network tab when issue on standard reviews)
I suppose it’s not out of the question that it’s nothing to do with Omega, it’s just I’ve tested extensively with it on and off and the problem only ever happens with it on!
In any case, unless you can think of any other information I could give you which might help find the source of the issue, don’t worry about it. I’ll disable Omega on everything except self-study and just accept it there
I’ll have another look at it this week
Hey, I want to let you know that I have encountered this problem in my own reviews. When using lightning mode (through Double Check) it manifests as a delay before moving on to the next item. This is presumably the same issue as you have been experiencing. So far I have not looked into it any further, but hopefully I will be able to track it down now
I’m not sure if it is the same issue as you are experiencing, but the issue that I have found is indeed due to the script not taking advantage of WK’s caching. Are you experiencing this when your queue is less than 110 items? At that point WK’s caching kicks in by default (in a sense), and I don’t experience the issue anymore.
Hmm, I couldn’t say for sure but that would definitely explain why it only happens occasionally lots of times at once. And I do think I remember it always happening with a longer queue!
Also it would only happen when you’ve completed BOTH the meaning and reading question for an item
Again, couldn’t say for sure but from what I remember of when it happens that would make sense. Good luck finding a fix if there is one!
I still think that it would make sense if WK would “fix” this by making their caching more robust against queue changes performed by userscripts:
I think userscripts don’t have easy access to the WK caching functionality to fix it themselves, so this small change in the WK code in
queue.js would probably be the best solution.
@Mods If I want to suggest a code change, is it better to send an email, or is it enough to tag Mods or a developer?
Having the same issue:
Using Firefox, no remaining counters in the upper right corner.
Tried in Chrome with only Open Framework and Reorder Omega installed, no counters as well.