[Userscript] Wanikani Heatmap

WaniKani API And Third-Party Apps
1691

so what did you do to fix it?

1692

Refreshing wof.file_cache doesnā€™t fix it for me unfortunately

1693

It just worked when I tried it again on a different dayā€¦

1694

With ā€˜reviewsā€™, it can also be the rate-limit on the server, which might make it pause for a minute (60 seconds) before resuming again. But if it doesnā€™t, refreshing the cache file is the usual fix, as others have said.

2 Likes
1695

yeah refresh, that didnā€™t work, but I am getting this:
image

1696

Hmm, thatā€™s ā€œservice unavailableā€. Could be a temporary glitch in the matrix. But if it persists, Iā€™d ask Tofugu.

Side comment: I noticed that my own WK account stopped working on my own wkstats site due to certain WK API queries taking too long. I havenā€™t reported it because Iā€™m done with my WK journey and didnā€™t figure it was a priority. (Plus I know that timed-out queries show up in a report, so theyā€™ll see it eventually, which is soon enough for my purposes)

2 Likes
1697

Little frustrating because under Chrome it works. - Maybe I will just switch to one and only google for heatmap. :-/

1698

Iā€™m in the opposite situation, itā€™s not working for me on chrome so I might have to switch to a different browser for the script until it eventually stops working there too.

1699

Soā€¦ Iā€™ve noticed that on my dashboard the time it takes for the heatmap to load is mostly governed by the Apiv2 retrieval of the reviews via the review cache, which it does with a filter with updated_after.

Iā€™ve locally tweaked it by first checking against the datetime of the last review session. Iā€™m assuming here that there is no point in trying to fetch reviews if theyā€™ve been fetched since the last review session already, regardless of how long ago that was. I think offline reviews on a phone app will also be visible on the review overview page once they are syncā€™ed.

        // Modified to only check for new reviews if a review session occurred in the mean time
        async function update_data_after_session(data) {
            if (!data.cache_version || data.cache_version < cache_version) data = {cache_version, date: "1970-01-01T00:00:00.000Z", reviews: [],}

            // insert extra check
            var lastReviewSessionDate = wkof.load_file('/review').then(parse_last_review_session, fail_last_review_session);
            if (lastReviewSessionDate) {
                if (new Date(lastReviewSessionDate).getTime() < new Date(data.date).getTime()) {
                    // no new review sessions since last fetch, simply returned cached data
                    return data.reviews;
                }
            }
            // else fetch new
            // end insert extra check

            let [date, new_reviews] = await fetch_new_reviews(data.date);
            if (new_reviews.length) {
                for (let new_review of new_reviews) data.reviews.push(new_review);
                data.reviews.sort((a,b) => a[0]<b[0] ? -1 : 1);
                data.date = date;
                save(data);
            }
            return data.reviews;

            //====================
            function parse_last_review_session(html) {
                return $(html).find('#last-session-date time')[0].getAttribute('datetime');
            }
            function fail_last_review_session(reason) {
                console.log("failed to check last review session date: " + reason);
                return null;
            }
        }

Locally this speeds up the loading of the heatmap considerably (provided Iā€™ve not run review sessions that is). Wondering if you think this is a good idea to include.

8 Likes
1700

Not Kumirei, but I like this idea

1 Like
1701

Not not Kumirei, but this is a great idea!

4 Likes
1702

Not not Kumirei enough

1 Like
1703

1 Like
1704

Hey, absolutely love the script!

Hereā€™s a little bug thatā€™s been bothering me for a while though:

image
image551Ɨ587 53.3 KB

The info spills out and can often be unreadable

2 Likes
1705

Oh, thatā€™s not right! Will look into it when I get the time

2 Likes
1706

Quick question out of interest: does the heatmap fetch all your reviews on each page refresh? If so, why doesnā€™t it only fetch new reviews since the last fetch, wouldnā€™t that massively speed it up? Sorry if Iā€™m missing something obvious, Iā€™m just curious about it :sweat_smile:

1 Like
1707

The heatmap caches your old reviews :wink:

1 Like
1708

It does cache your reviews, however, the issue is that in the last few months WK has had extremely slow response times on the reviews API, so just fetching the new reviews takes a very long time. @rwesterhof has provided an update to the script which will at least make it faster when there are no new reviews, but I havenā€™t found the time to merge it yet. Hopefully in a few days

3 Likes
1709

Hello, currently I also have the problem of my reviews not fully loading. I did my reviews on my phone for a while, so I have a lot of new reviews to load, but the last request stays at pending and after about a minute changes to 503 with some errors in the console.
image
image
Last time this problem was mentioned here it seems that it went away after a few days, but I wanted to ask if there a some things I could try to fix this. I have cleared the cache, restarted the computer, have only used Open Framework and Heatmap, Open Framework being before Heatmap and i dont have any adblockers installed.

1 Like
1710

Iā€™m sorry, I have no idea why this is happening. It is very strange that the previous request go through but that one is blocked by CORS. Also it shouldnā€™t thake that long for the request. Perhaps the CORS issue is related to the long response times weā€™ve been seeing on the reviews endpoint. @Mods do you know if the engineering team has looked into this yet? @skatefriday said they sent you an email in February

2 Likes