Martin

~~You are running into this issue https://github.com/elastic/beats/issues/20053#issuecomment-1899155624~~ You are JSON decoding your log three times. First time by adding the `container` input. Second time by adding the `json` keys to...

packr isn't used for much it looks like, these should be all of the affected files that need to be changed: ```bash deployment/semaphore.spec:##go install github.com/gobuffalo/packr/v2@latest go.sum:github.com/gobuffalo/packr v1.10.4 h1:k/aQq1+9UlSxfr9+QXz1sQ8vJVFTXqrEDdKgeonlt4Y= go.sum:github.com/gobuffalo/packr v1.10.4/go.mod...

Seems fixed, thanks! https://github.com/ansible-semaphore/semaphore/commit/67954b95aafe047856d9d2bb5fd539d17686b118

@geerlingguy How would I go about testing against my own image? I see that the molecule tests try against your own repository but you do not have one set up...

I've dropped the test and added the meta.yml entry for now. > Arch likes to update things quite rapidly, so maintenance (where I like to stick to a particular version,...

Either that or make a rule in your web server.

Yes. This seems to be the query code on my P85 - ```0702002a006000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000``` However decoding the response is gonna take me a bit. It seems like the response is current...

I figured enough to show current DPI. Still trying to figure out those 8 magic bytes that change with any change of anything, so likely no possibly to set DPI...

Ok so apparently you cannot get *current* DPI set on the mouse. Bloody software simply sets DPI to whatever it was last time you ran the software and afterwards it...

This repo is dead, since you're on Arch, use aur/a4tech-bloody-driver-git Still a dead repo(it is mine), but less dead than that and should work with your mouse.