fabic_ has joined #rust-embedded
starblue1 has quit [Ping timeout: 252 seconds]
starblue1 has joined #rust-embedded
fabic_ has quit [Ping timeout: 252 seconds]
<re_irc> <@newam:matrix.org> adamgreig: so I did a mock up for the cortex-m CI: https://github.com/newAM/totally-not-a-cortex-m-fork/commit/dd83fc0d3afcea7eab0eea36b317dd712085ec7f
<re_irc> <@newam:matrix.org> and an intentionally failing ci run: https://github.com/newAM/totally-not-a-cortex-m-fork/runs/3786325339?check_suite_focus=true
<re_irc> <@newam:matrix.org> There will be some nasty bootstrapping to prevent dependency cycles with cortex-m-rt. Not sure if there is a cleaner way to handle that. Any ideas?
<re_irc> <@newam:matrix.org> I was going to do something fancy with the CI system, but at the end of the day if this is going to be automatic it will be executing untrusted code, no way around that.
fabic_ has joined #rust-embedded
fabic_ has quit [Ping timeout: 245 seconds]
PyroPeter has quit [Ping timeout: 246 seconds]
PyroPeter has joined #rust-embedded
hosewiejacke has joined #rust-embedded
hosewiejacke has quit [Quit: Leaving]
<re_irc> <@adamgreig:matrix.org> I think the best way around the bootstrapping problem is to move cortex-m-rt into the cortex-m repository
<re_irc> <@huszty:matrix.org> Hey! Noob Rust user here! Is this the place to ask some very basic stm32 related questions?
<re_irc> <@9names:matrix.org> if you're asking stm32 specific questions, probably best to do so in #stm32-rs
<re_irc> <@adamgreig:matrix.org> (that's #stm32-rs:matrix.org , though you're welcome to ask here too if you like!)
fabic_ has joined #rust-embedded
tokomak has joined #rust-embedded
fabic_ has quit [Ping timeout: 260 seconds]
tokomak has quit [Read error: Connection reset by peer]
fabic_ has joined #rust-embedded
fooker has quit [Quit: WeeChat 3.1]
fabic_ has quit [Ping timeout: 252 seconds]
xnor has joined #rust-embedded
xnor has quit [Changing host]
emerent has quit [Remote host closed the connection]
emerent has joined #rust-embedded
fooker has joined #rust-embedded
fabic_ has joined #rust-embedded
fabic_ has quit [Ping timeout: 260 seconds]
flatwhatson has quit [Read error: Connection reset by peer]
flatwhatson has joined #rust-embedded
emerent has quit [Ping timeout: 252 seconds]
emerent has joined #rust-embedded
xnor has quit [Ping timeout: 252 seconds]
xnor has joined #rust-embedded
<re_irc> <@adamgreig:matrix.org> i wondered why docs.rs wasn't building the new stm32ral release, even though it said the build went OK
<re_irc> <@adamgreig:matrix.org> it turns out it generates 1.2 million html files in the docs, and the `zip` crate version they were using had a bug where after 64K files it fails 💀
<re_irc> <@adamgreig:matrix.org> almost 10GB of (uncompressed) docs, it takes cargo doc 5 minutes to build 💀
<re_irc> <@adamgreig:matrix.org> newam: didn't take long https://github.com/stm32-rs/stm32-rs/issues/642
<re_irc> <@adamgreig:matrix.org> pretty sure that would have been the awful linker error if the old versions weren't yanked
<re_irc> <@newam:matrix.org> That is a significantly better error message which is nice.
<re_irc> <@newam:matrix.org> Yeah, sounds like it is unrelated to the yanking, but people are seeing the new error message instead of the old linker error message.
<re_irc> <@ryankurte:matrix.org> hey i'm having a weird time with the SAMD51 and RTIC, probably need to put together a minimum repro but, does this seem familiar to anyone?
<re_irc> <@ryankurte:matrix.org> https://github.com/atsamd-rs/atsamd/issues/501