activitywatch icon indicating copy to clipboard operation
activitywatch copied to clipboard

Sometimes it doesn't work

Open JQiue opened this issue 11 months ago • 2 comments

  • [x] I am on the latest ActivityWatch version.
  • [x] I have searched the issues of this repo and believe that this is not a duplicate.
  • OS name and version: Windows 10
  • ActivityWatch version: 0.12.2

Describe the bug

For a lot of the time it didn't seem to record my behavior

Here are some logs

aw-watche-afk

2024-03-07 22:02:58 [INFO ]: aw-watcher-afk started  (aw_watcher_afk.afk:60)
2024-03-07 22:02:59 [WARNING]: 502 Server Error: Bad Gateway for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-afk_DESKTOP-RFAMSDK  (aw_client.client:35)
2024-03-07 22:02:59 [WARNING]: Not connected to server, 0 requests in queue  (aw_client.client:502)
2024-03-07 22:03:09 [WARNING]: 502 Server Error: Bad Gateway for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-afk_DESKTOP-RFAMSDK  (aw_client.client:35)
2024-03-07 22:03:09 [WARNING]: Not connected to server, 1 requests in queue  (aw_client.client:502)
2024-03-07 22:03:19 [WARNING]: 502 Server Error: Bad Gateway for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-afk_DESKTOP-RFAMSDK  (aw_client.client:35)
2024-03-07 22:03:19 [WARNING]: Not connected to server, 1 requests in queue  (aw_client.client:502)
2024-03-07 22:03:29 [WARNING]: 502 Server Error: Bad Gateway for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-afk_DESKTOP-RFAMSDK  (aw_client.client:35)
2024-03-07 22:03:29 [WARNING]: Not connected to server, 2 requests in queue  (aw_client.client:502)

aw-watcher-window

2024-03-07 22:02:58 [INFO ]: aw-watcher-window started  (aw_watcher_window.main:62)
2024-03-07 22:02:59 [WARNING]: 502 Server Error: Bad Gateway for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-window_DESKTOP-RFAMSDK  (aw_client.client:35)
2024-03-07 22:02:59 [WARNING]: Not connected to server, 0 requests in queue  (aw_client.client:502)
2024-03-07 22:03:09 [WARNING]: 502 Server Error: Bad Gateway for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-window_DESKTOP-RFAMSDK  (aw_client.client:35)
2024-03-07 22:03:09 [WARNING]: Not connected to server, 4 requests in queue  (aw_client.client:502)
2024-03-07 22:03:19 [WARNING]: 502 Server Error: Bad Gateway for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-window_DESKTOP-RFAMSDK  (aw_client.client:35)
2024-03-07 22:03:19 [WARNING]: Not connected to server, 5 requests in queue  (aw_client.client:502)
2024-03-07 22:03:29 [WARNING]: 502 Server Error: Bad Gateway for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-window_DESKTOP-RFAMSDK  (aw_client.client:35)
2024-03-07 22:03:29 [WARNING]: Not connected to server, 6 requests in queue  (aw_client.client:502)
2024-03-07 22:03:39 [WARNING]: 502 Server Error: Bad Gateway for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-window_DESKTOP-RFAMSDK  (aw_client.client:35)
2024-03-07 22:03:39 [WARNING]: Not connected to server, 7 requests in queue  (aw_client.client:502)
2024-03-07 22:03:49 [WARNING]: 502 Server Error: Bad Gateway for url: http://127.0.0.1:5600/api/0/buckets/aw-watcher-window_DESKTOP-RFAMSDK  (aw_client.client:35)
2024-03-07 22:03:49 [WARNING]: Not connected to server, 9 requests in queue  (aw_client.client:502)

To Reproduce

Expected behavior

Documentation

Additional context

JQiue avatar Mar 07 '24 14:03 JQiue

can you access the webui on localhost:5600 when this happens?

brayo-pip avatar Mar 08 '24 07:03 brayo-pip

can you access the webui on localhost:5600 when this happens?

yes, i can

JQiue avatar Mar 08 '24 12:03 JQiue