GrantM11235[m] has quit [Quit: Idle timeout reached: 172800s]
vancz has quit [Server closed connection]
vancz has joined #rust-embedded
cr1901 has quit [Read error: Software caused connection abort]
cr1901 has joined #rust-embedded
jasperw has quit [Server closed connection]
jasperw has joined #rust-embedded
mkj[m] has quit [Quit: Idle timeout reached: 172800s]
kline has quit [Read error: Software caused connection abort]
kline has joined #rust-embedded
MaartendeVries[m has joined #rust-embedded
<MaartendeVries[m>
<thejpster[m]> I’m also not convinced it’s not a breaking change because there might be a bunch of trace level logs out there that do not work and we’d suddenly break all those builds. I agree it’s better to check them but we don’t have the luxury of breaking changes in defmt due to how it works (with magic extern...
<MaartendeVries[m>
ah, interesting concern. I suppose we could hide this behind a feature flag
<MaartendeVries[m>
although a feature flag could be enabled by a rogue dependency
<MaartendeVries[m>
could do it with an env variable too DEFMT_CHECK=1 or similar
<MaartendeVries[m>
then it can only be done (reasonably) by the end user
<MaartendeVries[m>
it's less standard though
<MaartendeVries[m>
but defmt already uses DEFMT_LOG, so it won't be that strange
sroemer has joined #rust-embedded
sroemer has quit [Changing host]
sroemer has joined #rust-embedded
<MaartendeVries[m>
Could also decide to flip it: break things that don't compile, but allow an opt-out with DEFMT_NO_CHECK_DISABLED
MovementNetwork[ has quit [Quit: Idle timeout reached: 172800s]
<JamesMunns[m]>
Is anyone here good at some kind of graphing and/or visualization tool in Rust? I want to have a visualization/graphing/modeling example for ergot, and could use some help :)
<JamesMunns[m]>
I'd love to have some visual demos of this I could use. If someone is interested, I can get you some recorded data and a small app to replay it for testing.
Kaspar[m] has joined #rust-embedded
<Kaspar[m]>
<thejpster[m]> Sorry. I am completely rushed off my feet currently....
<Kaspar[m]>
I get that. Also, the support/maintenance track record is fine. Still I feel a bit alarmed, defmt is pretty central to the embedded Rust ecosystem, and this sounds a bit as if maintenance is now mostly reduced to paying Ferrous Systems customers.
<Kaspar[m]>
* reduced to the needs of paying Ferrous, * Systems customers. (edited)
<JamesMunns[m]>
That would be great! Mostly looking for someone who can throw something like that together quickly, because I haven't done it before :D
<dirbaio[m]>
<thejpster[m]> I’m also not convinced it’s not a breaking change because there might be a bunch of trace level logs out there that do not work and we’d suddenly break all those builds. I agree it’s better to check them but we don’t have the luxury of breaking changes in defmt due to how it works (with magic extern...
<dirbaio[m]>
This is a bug in users code, it's okay to break imo
<dirbaio[m]>
Defmt shouldve been typechecking all logs unconditionally, it's a bug that it accepted broken disabled logs and that pr fixes this bug
<dirbaio[m]>
Making the fix opt-in is unnecessary complexity and won't achieve anything because it's not discoverable, almost no one will use it
glitchy has quit [Remote host closed the connection]
glitchy has joined #rust-embedded
<thejpster[m]>
<dirbaio[m]> Defmt shouldve been typechecking all logs unconditionally, it's a bug that it accepted broken disabled logs and that pr fixes this bug
<thejpster[m]>
It would be great if you could add that comment to the ticket
<thejpster[m]>
<Kaspar[m]> I get that. Also, the support/maintenance track record is fine. Still I feel a bit alarmed, defmt is pretty central to the embedded Rust ecosystem, and this sounds a bit as if maintenance is now mostly reduced to paying Ferrous Systems customers.
<thejpster[m]>
Maintenance will obviously continue - defmt is important to us, not least because it’s central to our embedded training. I’m just pointing out there’s an alternative path that gets it raised up my priority list.
<thejpster[m]>
Also CI is broken and I need to sort that out. I’m now getting an unescaped quote in a JSON string and it makes the parser crash.
<JamesMunns[m]>
<thejpster[m]> Maintenance will obviously continue - defmt is important to us, not least because it’s central to our embedded training. I’m just pointing out there’s an alternative path that gets it raised up my priority list.
<JamesMunns[m]>
Is ferrous willing to take on non-fs maintainers for defmt? Not volunteering personally, but similar to recent additions to heapless maintainers, that could be an option.
corecode[m] has quit [Quit: Idle timeout reached: 172800s]
<dirbaio[m]>
Better than "pay us or your pr doesn't get looked at", definitely 😅
jannic[m] has quit [Quit: Idle timeout reached: 172800s]
i509vcb[m] has quit [Quit: Idle timeout reached: 172800s]
newam[m] has quit [Quit: Idle timeout reached: 172800s]
RockBoynton[m] has quit [Quit: Idle timeout reached: 172800s]
rmsyn[m] has quit [Quit: Idle timeout reached: 172800s]
ryankurte[m] has quit [Quit: Idle timeout reached: 172800s]
bartmassey[m] has quit [Quit: Idle timeout reached: 172800s]
therealprof[m] has quit [Quit: Idle timeout reached: 172800s]
glitchy has quit [Remote host closed the connection]