Closed blaa closed 1 year ago
Hi @blaa, thank you for your report.
Can you please try if this problem still occurs with following version of probe-run
?
$ cargo install --git https://github.com/knurling-rs/probe-run --branch fix-401
👋🏾
Yeah, just tried it (did a repro first, then command above and rerun code) and it seems to have fixed that. Thanks. ;)
Got back to cargo install --git https://github.com/knurling-rs/probe-run
and problem strikes immediately. Just to confirm.
Hello, thanks for this software. I've setup a project with defmt and probe-run today for the first time, so beware that I might be misguided. ;-)
When testing with a heavy traffic using RTIC (idle task spams a message and separate tasks sends one every 100ms) I reproductibly (but after a random time) get an error using a defmt-brtt logger. defmt-rtt logger seems ok.
At first I thought it's just a bit error on a cable - that can happen. But with a single task, or on defmt-rtt it didn't appear.
Main bug: https://github.com/datdenkikniet/defmt-brtt/issues/1
I still think, that if the RTT protocol can recover from this problem then probe-rs should log it as a warning, ignore it and try to continue with the application.
This time after 234922 messages, around 30s runtime. Or after 805335 idle messages, 1:49 measured.
Code: https://github.com/knurling-rs/probe-run/blob/5d20b3c21e0874b97f1fe79c671e3d372fc69c42/src/main.rs#L423-L448 Function can return Nones, so maybe it's fixable?