Closed renyuneyun closed 9 months ago
Thank you. With autostart_modules = ["aw-server-rust", "aw-awatcher"]
it works ok because the rust server starts up fast, I guess. Which may be why I didn't notice the problem.
Python client has a reconnect feature, and Rust client doesn't, that's a deficiency. I've added a quick workaround with 2 retries after 1s: https://github.com/2e3s/awatcher/releases/tag/v0.2.3
Thanks for the swift update. I can confirm it's working now.
Based on your experience, do you think aw-server-rust is stable enough for daily use (personal use)? I'm hesitating to whether switching to it or not.
Based on your experience, do you think aw-server-rust is stable enough for daily use (personal use)?
I've never faced any problem. However, I've started to use it since the beginning. Python and Rust servers use different folders for storage, I don't know if data can be just copied.
I'm trying to make aw-qt autostart awatcher. From the explanations, I now install awatcher's binary to
/usr/bin/aw-awatcher
. (I'm on archlinux.) Then, I changed~/.config/activitywatch/aw-qt/aw-qt.toml
, with the following content:(Tried changing order. Doesn't make any difference.)
During test, I verified that no activity process is running. Then, I launched
aw-qt
from terminal. However, awatcher is not correctly launched. In my terminal, I get the following:Now, aw-server is running, but aw-qt is not (nor is aw-awatcher). If I start aw-qt again, aw-awatcher will start, though aw-qt is still not, with that same symbol error, and error on port occupying (because aw-server is already running). So that symbol error seems to be related to aw-qt's tray icon itself.
I suspect this is because aw-qt starts all modules simultaneously, and awatcher quits itself while aw-server is still initializing.