Can't build with defmt-decoder 0.3.10

[tommy-gilligan]

Can't build with defmt-decoder 0.3.10

[tommy-gilligan]

We probably want to pin defmt-decoder 0.3.9 for now

[Yatekii]

We should report this as an upstream issue in https://github.com/knurling-rs/defmt too. They broke semver as it seems.

[tommy-gilligan]

We should report this as an upstream issue in https://github.com/knurling-rs/defmt too.

Agreed

They broke semver as it seems.

I'm not too clear on this. I didn't have time right now to properly investigate but probe-rs is using defmt-decoder with feature unstable. I think they did still break semver but potentially they're treating stuff we're using as breakable because of the feature flag?

[tommy-gilligan]

I can report to them if you'd like me to? Or I'll leave for you. Just let me know either way.

[Yatekii]

Hmm I did not consider the "unstable" flag. I find this a bit odd imo. In that case it's actually no breakage and we don't need to report 🤔
They already opened #2153.

[Cydget]

Is there a temporary bypass for this at the moment? I want to install probe-rs with ftdi feature. I was able to install it with cargo binstall , but that did not detect the ftdi probe I have.

[Cydget]

Is there a temporary bypass for this at the moment? I want to install probe-rs with ftdi feature. I was able to install it with cargo binstall , but that did not detect the ftdi probe I have.

Disregard my previous comment, doing what you said allowed me to compile from source.

We probably want to pin defmt-decoder 0.3.9 for now

[tommy-gilligan]

you should be able to

cargo install probe-rs --features cli,ftdi --git https://github.com/probe-rs/probe-rs.git

although trying this just now, i get a message about ftdi not being a feature, so i'm probably doing something wrong

[Cydget]

you should be able to

cargo install probe-rs --features cli,ftdi --git https://github.com/probe-rs/probe-rs.git

although trying this just now, i get a message about ftdi not being a feature, so i'm probably doing something wrong

I'm guessing they merged it as a default feature. I was following the guide here https://probe.rs/docs/getting-started/installation/ where it said the same thing. Even without specifying the ftdi feature the debug build detected my probe where the cargo binstall version did not. Either way, im able to continue as is.