Open timwsuqld opened 3 years ago
I think the reason is that aw-server-python accepts both a list of events as well as a signe event on the /api/0/buckets/bucketname/events
endpoint while aw-server-rust only accepts a list of events so it's not really 100% API compatible.
I think it's better if a HTTP endpoint only accepts a single type for its request as that makes the API consistent and easier to document so I'd prefer that the watcher changed the way it sends events. Do you agree @ErikBjare?
@johan-bjareholt I agree.
I also notice that aw-watcher-jetbrains seems to not use the heartbeat API, which may make it unreliable.
Edit: Looks like it is pretty unreliable and doesn't work as is intended. See https://github.com/OlivierMary/aw-watcher-jetbrains/issues/61 and https://github.com/OlivierMary/aw-watcher-jetbrains/issues/30.
https://github.com/OlivierMary/aw-watcher-jetbrains
Running activitywatch-0.9.2
There seems to be an issue with the JSON being sent, but because we don't appear to have
--log-json
in aw-server-rust I can't work out what the issue is.This is the output from aw-server-rust
And this is debugging from aw-server showing the json (edited to protect some data)
I'm not sure if this is a bug in aw-server-rust or aw-watcher-jetbrains, but there is a compatability issue. If you can let me know what the problem is (and/or how to get log-json in aw-server-rust) then I can help aw-watch-jetbrains implement the fix if that's what's needed.