No stats from plugin

[toptalo]

Hello!
After update to version 4.0.2 I have not see any stats from plugin in dashboard
Is it work?

[AxeR21]

I'm encountering the same issue even with 4.0.3.
In Chrome DevTools there's the following error:

Uncaught (in promise) NotFoundError: Failed to execute 'transaction' on 'IDBDatabase': One of the specified object stores was not found.
    at Proxy.n (index.js:125:26)
    at Proxy.r (index.js:228:25)
    at Object.sendHeartbeats (WakaTimeCore.ts:178:49)
    at async background.ts:12:19

[alanhamlett]

I've renamed the IndexedDB database and bumped the db version so it's re-created fresh in v4.0.4. Does that fix it?

Duplicate of #286.

[AxeR21]

Is it normal i see version 4.0.3.2?
Now it seems to work but I had to remove and add extension again to Chrome because evene after upgrading and closing/opening Chrome the issue was still present.
I've noted that in config is still present queueName: 'heartbeatQueue',

In console there are a couple more errors:

Heartbeat 0 returned status: 202
(anonime) @ WakaTimeCore.ts:232
Heartbeat 1 returned status: 202
(anonime) @ WakaTimeCore.ts:232
Heartbeat 2 returned status: 202
(anonime) @ WakaTimeCore.ts:232
Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.
    at l (browser-polyfill.js:1154:18)

[alanhamlett]

It's v4.0.3.2 because I reverted a rollback and chrome doesn't allow duplicate versions.

Those errors will go away with v4.0.4.

[AxeR21]

Now I'm on 4.0.4 and it does register stats successfully. There's still the browser-plolyfill error.
Thanks for the amazing support and quick resolution

[sjclayton]

Stats not being reported for me here on Firefox using 4.0.4, it's been over a week (probably from around v3.0.22) since I've had anything reported from in Firefox, I use wakapi.dev... Just actually noticed this yesterday, thought something looked off with my times.

All my other plugins (editors) work with my wakapi instance still... just not the browser extension, nothing changed with my setup other than updating the extension.

[toptalo]

Updated to 4.0.4 and now looks like all works fine

Thanks!

[Atko]

@sjclayton that's probably related to the issue #282. I have the same problem under ffox since the plugin version 3.0.24.

[alanhamlett]

@sjclayton is it working with v4.0.5?

[sjclayton]

@alanhamlett No it's not... it can't seem to hit the endpoint on my wakapi instance at all now... I keep seeing 404's even trying to retrieve the today's time.

Seems like you are appending additional duplicate API path's on top of what wakapi is already expecting, and that is making it 404 on everything. The extension can't get a total daily time, let alone that it still does not appear to be even trying to send heartbeats to the wakapi instance. Like I see zero POST requests in my logs, not even attempts that end up failing.

[alanhamlett]

What's your API url setting set to?

[sjclayton]

This is what was working previously, before the extension was updated.... which I figure things broke sometime around v3.0.22-3.0.24

https://waka.clayton-tech.ca/api/compat/wakatime/v1

That is the API url I have set for the extension, it's for my self hosted wakapi instance, it's not publicly accessible.

Now any GET requests the extension is trying to send are failing, because it seems to be appending /api/v1 to the end of the existing url, even though it shouldn't need it. Also like I said I see no POST attempts even with the messed up API path.

[alanhamlett]

Try with v4.0.6.

[sjclayton]

The GET requests appear to be returning 200 now... but I still see no daily total time in the extension, and it's still not sending heartbeats (zero POST requests at all) to the wakapi server.... so it's back to where it was as of v4.0.4 from what I can see.

[sjclayton]

@alanhamlett

Quick question -- has the format for associating sites to a "Project" changed recently...? I have the extension set to only log allowed sites.

The format I use for a site is this, example:

https://github.com@@code to log all github.com accesses with the project / tag "code"... this is what has previously worked.

Just want to double check, just in case something has changed that I need to update with the URL's for the sites I track.

[alanhamlett]

Yes, we changed the format to remove @@ and have a structured UI for customizing projects.

[sjclayton]

@alanhamlett

Ok... I don't actually use Wakatime directly, only Wakapi... so therefore I don't login to the extension... is there any way to do this in the extension without using a Wakatime account?

If not then I won't be able to make use of Wakapi with the extension anymore for tracking websites, and will only be able to use the editor plugins. 😞

[alanhamlett]

Login happens when you enter your api key, it doesn't mean you need to actually login to any website.

[sjclayton]

@alanhamlett

Ok, but this new structured UI for specifying projects associated to a URL that you mentioned is no where to be found in the extension in Firefox.. is there something I'm missing?

That is what I was trying to get at in my last comment, if it involves something I can't directly do in the extension or in some other way... then I won't be able to track things the way I need to anymore.

[alanhamlett]

Click the extension icon, then click Options and look for these two sections:

Here's the Only track these sites setting:

And the separated out Custom project names setting:

[sjclayton]

Holy shit I'm blind.... Nevermind, I was just in there earlier to grab the API url and looked right at that too, and wondered what it was...

Maybe that's why I asked about the "@@", my brain does weird things like that...

[alanhamlett]

Closing this because it's most likely due to the only track allowed sites setting.

[alanhamlett]

@sjclayton the reason it's not working for you is this:

muety/wakapi#688

You can modify the browser extension to remove id from the JSON post payload, and convert time from String to number. Run npm i then run npm run build and load the unpacked extension from the resulting dist/chrome folder.

That way it will work right away instead of waiting for the issue to get fixed.

[sjclayton]

@alanhamlett

Thanks for the prompt replies, I will follow the wakapi issue so I know when things are fixed on their end. 😃

[rob4226]

I changed this line in the browser extension:

browser-wakatime/src/core/WakaTimeCore.ts

Line 187 in 77d0963

return { ...heartbeat, userAgent };

to:

return { ...heartbeat, userAgent, id: undefined, time: +heartbeat.time };

to get the browser extension to work in the meantime.

Edit:
@alanhamlett Yes, that's true. For some reason I thought heartbeat.time was some ISO type date string. I updated the code above to use the real heartbeat time.

[alanhamlett]

This is better to not overwrite the heartbeat timestamp:

return { ...heartbeat, userAgent, id: undefined, time: Number(heartbeat.time) };