Karl Palsson
Karl Palsson
So, the "cancelled" runs, no idea. the failing checks are completely outside my code. The flake validation errors have been in the code since at least 3343eff8 in 2017 (edas/tools.py)...
Perhaps describe what the goal is here, and the behaviours that can't be managed with existing tooling?
I'm pretty sure I was seeing this as well today. That "expiring client local.blah due to timeout", and with zero extra info available. In my case I was only bridging...
I had this as well, updating from 22.03 "ealier" to 22.03.2 f3ffb04a43..00d7702796 to be precise. A make dirclean fixed it. (I was building for ath79, not mvebu)
@David-OConnor Did you get these examples sorted out? I've got the https://github.com/Tiwalun/stm32wb55-homekit/ demo running on my board, but having quite a bit of trouble back porting it to these examples....
Still, this may not be quite right.. the bitfields docs, https://docs.rs/bitflags/1.3.2/bitflags/#zero-flags, say "Users should generally avoid defining a flag with a value of zero." ? From reading what they're saying,...
I'm still working on your repo as the "upstream" at the moment, right? Things should go from your repo here, and then into stm32-rs eventually? The "goal" is for this...
This largely supersedes #4
This fixes #3 but, as before, I can't get the transparent mode example to build, there's usb problems I can't fix.
Ok, fixed the USB issue too now :)