Sebastian Thiel

Thanks so much for reporting and the deep analysis of the issue - it's much appreciated! Let me CC @PavelLaptev and @estib-vega for a fix :).

I will be making the worktree information discoverable in our workspace data structure, which then trickles through to the CLI that way. In theory, this makes it usable by the...

With #11123 there is a basis for bring worktree support closer to the vision presented here. For now, it looks like this: It's not meant to satisfy this issue, but...

Maybe what's happening here is that the backend doesn't get a secret even if it's present. Then the UI gets nothing, but sets "nothing" or clears the existing value 'by...

I wanted to hand this to AI but I keep thinking that adding Clits isn't the right prompt. Can you elaborate 😅?

Now I get it: A CliId is a short-id of sorts that's only valid in the CLI to refer to items when interacting with them.

The lack of detail is due to the [`source()` trail](https://doc.rust-lang.org/std/error/trait.Error.html#method.source) not being followed by the [routine that prints the error](https://github.com/RustSec/rustsec/blob/3544515990b09441ecc12df8d0291bc6f23d3d30/cargo-audit/src/auditor.rs#L73). `Display` will only display the error message of the respective...

Thanks for letting me know! After taking a quick look at `extract_tree()` I think It probably will take more to make this work. My thoughts are that first of all,...

Thanks a lot for reporting and for the suggestion! I agree that ideally, one can choose a ref that is unlikely to trigger additional side-effects.

Could the `_resumable` part be the issue? Is there a way to send it without streaming? I recommend vendoring the crate source code so it's possible to make local modifications...