You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi there,
I managed to install your ActivityWatch plugin, and it works well to report data.
I think there is a bug in the index.html file though.
Here is what the plot looks like, after precisely following the instructions from https://github.com/Alwinator/aw-watcher-utilization?tab=readme-ov-file#custom-visualizations
It's all skewed on a specific time, and does not show a nice plot with different point like on your example.
Thanks in advance, if you have time to investigate this issue.
I'm available to test any change to the index.html or to answer any question you could have regarding this issue.
Regards, -- @Naereen.
The text was updated successfully, but these errors were encountered:
Hi there @Alwinator :)
In the browser console I got the following message:
Unchecked runtime.lastError: The message `aw-watcher-utilization/:1` port closed before a response was received.
And maybe the next error message also concerns aw-watcher-utilization:
inject.js:1 [Deprecation] Listener added for a synchronous
'DOMNodeInserted' DOM Mutation Event.
This event type is deprecated (https://w3c.github.io/uievents/#legacy-event-types)
and work is underway to remove it from this browser.
Usage of this event listener will cause performance issues today,
and represents a risk of future incompatibility.
Consider using MutationObserver instead.
Hi there,
I managed to install your ActivityWatch plugin, and it works well to report data.
I think there is a bug in the
index.html
file though.Here is what the plot looks like, after precisely following the instructions from https://github.com/Alwinator/aw-watcher-utilization?tab=readme-ov-file#custom-visualizations
It's all skewed on a specific time, and does not show a nice plot with different point like on your example.
Thanks in advance, if you have time to investigate this issue.
I'm available to test any change to the
index.html
or to answer any question you could have regarding this issue.Regards, -- @Naereen.
The text was updated successfully, but these errors were encountered: