activitywatch: Unable to stop the stop watch

  • I am on the latest ActivityWatch version.
  • I have searched the issues of this repo and believe that this is not a duplicate.
  • OS name and version: Windows 7
  • ActivityWatch version: v0.11.0

Describe the bug

When I try to use the Stopwatch after updating it shows some TypeError after reloading the page the stopwatch seems to be running but again when trying to stop it ,it shows the same error so I have to delete that to stop it going on

To Reproduce

Steps to reproduce the behavior, for example: 1. Go to Stop Watch 2. Create a new stopwatch 3. TypeError: Cannot read property ‘timestamp’ of null. See dev console (F12) and/or server logs for more info,

See this gif kh5Fk8

Expected behavior

It does start the stop watch but I cannot stop it without deleting.

Documentation

image This is what appears after pressing F12 Key

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Reactions: 4
  • Comments: 28 (8 by maintainers)

Commits related to this issue

Most upvoted comments

@MohammedNoureldin Awesome, happy to hear it!

Let us know if you find any new issues in the nightly!

The stopwatch feature would be very useful when completed.

I believe the two files involved are:

Currently, whenever pressing “stop” an exception is being thrown, displayed in red at the top, and the stopwatch does not stop.

To be clear, I’m using v0.11.0

Screenshot from 2021-07-20 16-08-58

I tracked down the issue and made a PR in https://github.com/ActivityWatch/aw-core/pull/108.

Once it’s merged and the submodules in the main repo are updated it should (finally) work correctly!

This seems to be working! Thanks a lot @ErikBjare! I just had the issue when opening the page in the browser that I could not navigate anywhere, but refreshing hard-refreshing the page solved the issue and now everything seems to be good!

Once completed, this build should contain the fix: https://github.com/ActivityWatch/activitywatch/actions/runs/1242036227

If anything doesn’t work, let me know!

This was the main feature for me. I may be downgrading until the fix

I too have been encountering this.

I confirm build #199 is working for me. Thanks @ErikBjare !

Build #199 should contain the fix once CI passes.

If there are any more related issues, please let me know!

@MohammedNoureldin Sorry I was mistaken, it should finally be fixed in https://github.com/ActivityWatch/aw-webui/commit/7feadde52419ae5d4d1570a543421627f8158b1f

Next nightly will definitely contain it!

@MohammedNoureldin Ah yeah, sorry, I had not updated the webui submodule which contains the fix.

I just pushed a change with the updated submodule, so the next nightly build should have the issue resolved (just tested locally).