10:33 <Rustnoob[m]> Quick question...what's the correct way to disable all interrupt on nrf52 family with softdevice not enabled??

10:47 <dirbaio[m]> critical_section::with()

12:38 <ManuelHatzl[m]> <juliand[m]> "> <@mhatzl:matrix.org> Hi..." <- that would be a possible workaround, yes.... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/VBrjpGkSAObyMKFlcWtEiFqv>)

14:51 <RobertJrdens[m]> How do y'all use write!()/writeln!() against an embedded_io_async::Write? Anybody have a little wrapper ready that impls fmt::Write into a buffer and then async drains the buffer into the async::Write? Preferrably with an awrite!(async_write, stuff).await macro?

14:51 <JamesMunns[m]> The downside of the formatting machinery is that you can't really do it incrementally

14:52 <JamesMunns[m]> so you do usually need to format the whole thing into a buffer and then send it

14:52 <RobertJrdens[m]> I want to buffer

14:52 <RobertJrdens[m]> I think I said that.

14:52 <JamesMunns[m]> Yep! I wasn't sure what your awrite! macro would do

14:53 <JamesMunns[m]> (I would love to be able to incrementally format into a fixed size buffer, e.g. a 128 byte buffer, where even if the formatted string was a total of 512 bytes, you could alternate formatting and async sending; but you can't do this)

14:54 <JamesMunns[m]> but yeah, usually I writeln to a buffer, then do a normal async send(buf).await, I don't usually even macro it, but you could

15:03 <t-moe[m]> How do you guys extract test binaries built in a CI/CD pipeline?... (full message at <https://catircservices.org/_matrix/media/v3/download/catircservices.org/cYZqjzwnkHlAAiplwZVaUZXq>)

15:23 <thejpster[m]> I don't think I've ever built test binaries and then not just executed them immediately.

15:56 <vollbrecht[m]> <thejpster[m]> "I don't think I've ever built..." <- he wants to "immediately" execute them but they cant be run on the host machine, so he try's to get them and forward them.

16:00 <thejpster[m]> oh. Ferrocene does that, building aarch64 test binaries on Linux and then sending them over to an Aarch64 machine to execute. Pretty sure upstream Rust does it to.

16:00 <thejpster[m]> But I don't know how they do it. Probably not using `cargo test`

16:04 <vollbrecht[m]> t-moe: i don't know if that works but maybe we can convince that [out-dir](https://doc.rust-lang.org/cargo/reference/unstable.html#out-dir) unstable feature also works with test artifacts

16:04 <vollbrecht[m]> s/that/the/

16:06 <vollbrecht[m]> * t-moe: i don't know if that works but maybe we can convince the [out-dir](https://doc.rust-lang.org/cargo/reference/unstable.html#out-dir) unstable feature, to also work with test artifacts.

16:07 <thejpster[m]> t-moe: my esteemed colleagues tell me `cargo test --no-run --message-format=json` is a thing

16:15 <jessebraham[m]> Ooh that's good to know... thanks for that!

16:16 <vollbrecht[m]> can clean up [that](https://github.com/esp-rs/esp-hal/blob/main/.github/workflows/hil.yml#L76) abomination here now ? ;D

16:19 <vollbrecht[m]> though it works right? 😁

16:23 <jessebraham[m]> <vollbrecht[m]> "can clean up [that](https://..." <- Shhh 😂

16:23 <jessebraham[m]> Haha yeah it's been working, but is very much a temporary solution

17:03 <t-moe[m]> Nice. Thank you thejpster: