watcher afk / windows behind proxy (squid)
See original GitHub issueDescribe the bug
With my personal PC no problem, but at work with proxy for afk and windows watcher I have this error:
2019-01-22 12:02:24 [INFO ]: aw-watcher-afk started (aw_watcher_afk.afk:53)
2019-01-22 12:02:25 [WARNING]: 503 Server Error: Service Unavailable for url: http://localhost:5600/api/0/buckets/ (aw_client.client:72)
no problem with firefox plugin or other plugins
To Reproduce
Steps to reproduce the behavior:
- Setup squid proxy
- setup windows proxy to squid
- Start afk or windows proxy
Expected behavior
No bug
Environment
- ActivityWatch version: 0.8.0b7
- OS: Windows 10
Issue Analytics
- State:
- Created 5 years ago
- Comments:25 (15 by maintainers)
Top Results From Across the Web
squid : cache_peer configuration directive
Both Proxy- and WWW-Authorization headers are passed without alteration to the peer. Authentication is not required by Squid for this to work. Note:...
Read more >How to Setup Squid Proxy Cache on Windows in Azure/AWS ...
To install Squid Proxy Cache on Windows Server on any of the cloud platforms, the recommended way is to use our publicly available...
Read more >Untitled
Windows Only ! Have your bots work for you 24/7 Stockpile …. It is web protocol which permits client and server traffic cross...
Read more >Using the PortQry command-line tool - Windows Server
In some cases, PortQry may report that the System Idle process (PID 0) is using some TCP ports. This behavior may occur if...
Read more >Getting started - ActivityWatch
Download and run the Windows installer for the latest release on GitHub. ... a trayicon and automatically starts the server and the default...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

All is good now, that take 4-5h to consume ~1 month.
It is also a known bug that consuming the queue is much slower on windows than on macOS/Linux. The pre-merge events a few releases ago should have improved this a bit, but if the queue has days of events it might still take hours to be fully worked through. Exactly why it’s so slow on windows though I don’t know.