Mango The Fourth

issues persist on firmware built with the latest 3.5 container

https://hub.docker.com/layers/zmkfirmware/zmk-build-arm/3.5-branch-20231114235846-3.5.0-0.16.3-6c450465d1dd-6870957618/images/sha256-33cffa362f3613197c0c37788415271f534b80f168bb56650ba1419d2f03d46d?context=explore I used this one...

my github workflow runs west update; does the container not have the 3.5 zephyr? why was it named that?

https://github.com/NixOS/nixpkgs/issues/242313#issuecomment-1834653530

btmon --read works fine for me, apparently it uses some binary format when doing --write

Do I understand correctly, that to make this progress, we would first have to implement this proposal on the HUnit side of things?

aha, makes sense, do you perhaps happen to have insight on the decision process there?

heya @dpwright do you have any opinions on this PR? thanks in advance!

I mean it’s still safe, we’re just circumventing, for us, irrelevant roles. Surely though, just changing the key type would be good enough, if that was possible.

I have the same issue: ``` [2024-05-08 10:05:45.626] [info] Hyprland IPC starting [2024-05-08 10:05:45.626] [error] Hyprland IPC: Unable to connect? [2024-05-08 10:05:45.627] [error] Hyprland IPC: Couldn't connect to /tmp/hypr/cba1ade848feac44b2eda677503900639581c3f4_1715153733_548349008/.socket.sock. (3)...