Same thing was happening to me although it seems to be working again.
Seems to be the case, though itās still going a bit slow.
Good news is my progress wasnāt lost, after all! ^0^
Yeah site upgrade was a bit bumpy, should be recovering now. Just doing teh preliminary work to cut over to API v2
ćē²ćę§ć§ćļ¼
It seems to be working now
I canāt log in for some reason. I actually just reset my password, used said password, and Iām still getting āUnable to log in with provided credentials.ā
Huh thats odd, can you give me your username? or just email me more details?
Ah interetsing, looks like login via email is disabled. Try logging in with your username instead, while I whip up a fix.
This has now been fixed
Hey @Tadgh11,
I donāt seem to be getting any new reviews the last few hours. The number of upcoming reviews is going down (it was at 12 around 19:15 EDT, and is down to 11 now), and theyāre disappearing from the chart, but they never actually show up to do them.
I tried logging out and logging back in in normal mode, and also Incognito mode. Iām running Chrome 77 on Windows 10 and , and it was also happening on my Momās PC, running Firefox (not sure which version) on Windows 7.
My usernameās meekohaw, same as here.
Thanks,
meekohaw
Thanks for the quick fix! I assume this update is just to make the site compatible with the latest WK API? Is there anything in the foreseeable future thatāll be new for end users?
Check in a few min, should be good again.
Wellll a few things, but nothing to worry about for now
Now this is how you write an error report
I had some reviews this morning, so looking good. Weāll see what happens through the day today.
Thanks.
@Tadgh11
I have the same issue right now as @meekohaw had yesterday.
For a whole day I have zero reviews, all my upcoming reviews just disappears into the blue when it should show up on my review queue, but it doesnāt.
api/v1/review/counts/ says {āreviews_countā:0,ālessons_countā:0}.
api/v1/user/me/ says next_review_date: 2019-10-15T03:15:00.206047Z (Hmm, it looks like itās in the past.)
My username is HotAirGun.
Hey all, regarding the SRS issues. They should be fixed now! My apologies. Let me give you a rundown of what happened.
- I upgraded some core internal functionality of the site
- A bug in the code caused every single user to be triggered for a full sync back to Wanikani (this is a lot of users).
- Our asynchronous sync workers couldnāt keep up (KW is hosted on a pretty small machine) so I shut down the sync tasks until i can fix the bug
- Inadverdently, the SRS asynchronous task was also shut down
I have re-enabled SRS, so your reviews should magically pop back into life now.
Regarding new vocab/synonyms, once I write the fix I will re-enable the user syncing and we will be back up and running. Sorry about the downtime!
There still seems to be some oddness happening. I just had a review pop up for ę, which is level 26, while Iām only level 17.
The KaniWani item page says itās SRS level 5 on KaniWani, and SRS level 9 on WaniKani. It, along with its kanji and radical, are actually still locked on WaniKani, though.
In light of all the issues, Iām taking KW offline for an indeterminate amount of time until I can fix everything.
Looks like weāre back in business? ę is still showing up in my reviews, though.
Still a few kinks to work out. Iāll investigate that one separately: over-leveled vocabulary showing up Ā· Issue #460 Ā· Kaniwani/kw-backend Ā· GitHub . Very likely what happened is this:
- it used to be level 5
- you synced it to KW
- WK changed the level on it.
- You are still associated to it in KW.
If you donāt mind popping over into that github issue and and explaining what you feel the best behaviour in this case would be, I would appreciate it.