For the last couple of days (yesterday and today), whenever i start a review session, everything looks normal. And then as soon as I press the first key to type in the answer block for the first review:
Only on the very first one, not any others, no matter how long my session is. It doesn’t happen UNTIL I start typing, even if I wait for it. And when I click refresh, it immediately continues with another review (no real connection problem). It’s weird, is all, and I haven’t changed anything on my end. I can still do my reviews just fine after I click through the “refresh?”
Second super-minor thing, more of a feature request than a bug really, but since I’m here:
This is how it should look right now. No reviews left, none until 9pm. So far so good. The not-really-a-problem is, after 9pm if I still have the tab open, it doesn’t change to say I have reviews. I just have to notice it’s after 9pm and refresh the page, before I can click to start the review session. It would be nicer if the reviews block auto-updated or something when reviews came due. (I swear older revisions of the front page used to update on their own, but I could be wrong about that)
I have been seeing the same thing but for several weeks now. Based on some initial investigation I think it might be related to one of the user scripts I am running. Will provide more info after I do my next step in checking this out.
The one thing I have noticed, which has been consistent, is that if I do NOT see the timeout issue for a review session then the SRS level indicator (coloured circles under the “You have lost connection…” message in the screen capture below) are present through out the review session. If I do encounter the timeout issue then post refreshing, the review session is fine but the SRS level indicator is missing. Which has me wondering if this is related to a user script (whichever one is providing that SRS level indicator add-on). However, from your screen shot I am not seeing that you have that script installed/active, so likely not the cause.
Your first issue happened to me a few months ago. It was a certain script causing it, I forgot which one though. Have you tried disabling all your scripts?
I’ve got a couple of scripts and I’ll try doing reviews with them off next time to see what happens. It’s just weird that it suddenly started happening after literal years of working fine with no changes on my side. The only thing I ever change is turning on and off 10ten reader, and that one’s off when I do reviews.
Nope, just got home and did a set, and it didn’t happen today. Noted that I had all the usual scripts on, 10ten reader was off. That was going to be the “reproduce the problem” baseline, and then my 5pm set I was going to change something. But then the problem didn’t happen.
I am still seeing it. A couple of times today thus far.
@WaniConti If there is any specific context/debugging info you would like collected when it happens, let me know and I will make a point of collecting it next time.
Hey mgrice! Yes!! Your browser and OS info (and version) and a screen shot of your web inspector console as the issue is occurring, if you don’t believe that it is a script issue.
Hmm… (I’m the author of that custom SRS script) I fixed an issue with that script that caused a similar issue with specific settings a couple of weeks ago, so if it wasn’t fully updated and you’d specifically disabled all the “item capture” settings then it could have been that. But if you hadn’t touched those settings in the script then there’s no known issue that could cause what you were seeing. Maybe a compatibility issue with one of your other scripts?
In all honesty I didn’t mess around too much trying to work it out. I downloaded it right after you released it, so I figured there would be some bugs that needed to be worked out at first, and I would try again at a later time. Later today I’ll re-enable the script and see if the issue is still there, and if it is maybe I can get some more details for you. (Then again, it’s entirely possible that the culprit was a different script and I’m just remembering wrong…)
Update: after re-enabling the script and trying reviews, the issue wasn’t there.
We can probably rule that out as I do not have that script installed, so it cannot be causing the issue for me. At some point, if I have some spare time I may take a deep debugging dive.
