Bucket not created about aw-watcher-input HOT 5 CLOSED

I lied, finally fixed in 9bb85c4

from aw-watcher-input.

I think I fixed this in 5ffcacd.

Please let me know if issues persist.

from aw-watcher-input.

Try manually creating the bucket.

I just did this by importing a fake JSON that I created myself, and it works!

For reference only, here was my JSON. If you wish to attempt the same trick, please be sure to replace the hostname with your own and (optionally) a more realistic creation timestamp.

{
   "buckets" : {
      "aw-watcher-input_hostname" : {
         "client" : "aw-watcher-input",
         "created" : "2022-01-08T19:17:19.456700+00:00",
         "events" : [],
         "hostname" : "hostname",
         "id" : "aw-watcher-input_hostname",
         "name" : null,
         "type" : "os.hid.input"
      }
   }
}

from aw-watcher-input.

Try manually creating the bucket.

I just did this by importing a fake JSON that I created myself, and it works!

For reference only, here was my JSON. If you wish to attempt the same trick, please be sure to replace the hostname with your own and (optionally) a more realistic creation timestamp.

{
   "buckets" : {
      "aw-watcher-input_hostname" : {
         "client" : "aw-watcher-input",
         "created" : "2022-01-08T19:17:19.456700+00:00",
         "events" : [],
         "hostname" : "hostname",
         "id" : "aw-watcher-input_hostname",
         "name" : null,
         "type" : "os.hid.input"
      }
   }
}

It worked, thanks

for those who do not know how to make the watcher start in login, you could use this command since poetry should be run in the same directory
(cd /home/mo/Downloads/aw-watcher-input && poetry run aw-watcher-input)

from aw-watcher-input.

The issue isn't really fixed. You shouldn't have to create the bucket manually, that's just a workaround.

from aw-watcher-input.