AxiosError: timeout of 30000ms exceeded

[flowingblaze]

I am on the Windows 10, ActivityWatch is v0.12.1 which is the latest version as of me writing this bug report.

Describe the bug

When you go to activitywatch's dashboard and click raw data, and try to do anything (like for example exporting a bucket or events) you will get an error of "AxiosError: timeout of 30000ms exceeded" that will duplicate if you try to export again or open a bucket. ## To Reproduce Steps to reproduce the behavior: 1. Go to 'ActivityWatch Dashboard' which is http://localhost:5600. 2. Click on 'Raw Data' on the top of the page 3. Click on a bucket and hit "export events as csv" 4. A few moments will pass where nothing happens, where you will see the error ## Expected behavior I expected to be able to export buckets as json and export events as csv, ## Documentation  ## Additional context I did have this problem months ago, but uninstalling and reinstalling activity watch did work but I lost all my data before uninstalling and I don't believe that is a proper fix to this issue

[github-actions[bot]]

Hi there! As you're new to this repo, please make sure you've used an appropriate issue template and searched for duplicates (it helps us focus on actual development!). We'd also like to suggest that you read our contribution guidelines and our code of conduct. Thanks a bunch for opening your first issue! 🙏

[BelKed]

Possible duplicate of https://github.com/ActivityWatch/activitywatch/issues/773 Please try with the latest beta v0.12.2b1

[flowingblaze]

Update: I was able to export two events as .csv. However I did get another "AxiosError: timeout of 30000ms exceeded" before I refreshed the page and It was able to work. The only thing that changed is that I uninstalled a watcher, particularly the obsidian plugin watcher. Although I have had this error before I installed the watcher, but that was back when the firefox extension was working. The only two working watchers right now are "aw-watcher-window" and "aw-watcher-afk". Maybe there's an issue when more then two watchers are installed?

[flowingblaze]

Possible duplicate of #773 Please try with the latest beta v0.12.2b1

Also I forgot to mention in my last comment, the beta makes the bug appear again. It's only when I have the two watchers in the non-beta version is when the bug dissapears.

[BelKed]

Oh, sorry, I somehow misread your issue description. My apologies for that.

As I'm thinking about this right now, I realized I experienced almost the same issue with a timeout on the Python server after using ActivityWatch for about a year. I simply switched to the Rust server (https://docs.activitywatch.net/en/latest/migrating.html), which solved the problem.

I think the problem is when there is more data in the database, so the Python server could not handle it.

[ErikBjare]

In the settings you can raise the 30000ms timeout to something higher, which would probably also work.

On Mon, Feb 20, 2023, 20:04 BelKed @.***> wrote:

Oh, sorry, I somehow misread your issue description. My apologies for that.

As I'm thinking about this right now, I realized I experienced almost the same issue with a timeout on the Python server after using ActivityWatch for about a year. I simply switched to the Rust server ( https://docs.activitywatch.net/en/latest/migrating.html), which solved the problem.

I think the problem is when there is more data in the database, so the Python server could not handle it.

— Reply to this email directly, view it on GitHub https://github.com/ActivityWatch/activitywatch/issues/847#issuecomment-1437438032, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAKXDORDSBXNUP2P5CJJWSDWYO53RANCNFSM6AAAAAAVAXLQQQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>