Viktor Vilhelm Sonesten

Cargo warnings/errors are not propagated when building target application

4

For example: non-applied patches.

Add functionality to export raw ITM trace

1

A lot of malformed packets are observed on my end when using an STLink probe (to a stm32f401retx). I recall there being less problems when a TTY source was used...

When cargo builds something, it will traverse directories upwards and look for `.cargo/config{,.toml}` files. If such a file is found when the intermediate library is built, something wrong is likely...

The hints of `cargo-flash` are hidden inside of the executable, and are not available via `probe_rs_cli_util` yet. Move `diag::DiagnosableError` there and refactor a bit. Then, for the error types in...

Gitlab integration?

7

This was asked during NixCon, but I figure I'll lift it here in order to track progress: is Gitlab in-scope, and if so, what work remains?

convert: Don't stop when files can't be copied

6

### Problem In the process of exporting my whole music library in a lossy format (`beet convert --dest /path/to/dest/`) I stumbled upon a few invalid database entries that stopped the...

This patch was written before I noticed the legal notice: feel free to discard (but please do apply explicit `O_CREAT` params to the client remoting code; it would simplify the...