Robin Krahl

@nestire I might have misunderstood your request because nitrokey-app2 and Qubes is directly linked to bootloader issues in my brain. ^^ You were actually referring to the FIDO2 reset, right?

Yes, that timeout is fixed.

@nestire Can you please confirm that this is about the FIDO2 reset?

Closing as wontfix as we have to comply with the spec for the FIDO2 reset.

I think re-exports do have some benefits. Especially for types like `heapless_bytes::Bytes` and `littlefs2::Path` that are fundamental to Trussed, it would be less convenient to always have to add heapless-bytes...

I still hope for a future where we don’t need the Git dependencies … or at least only in the runner, not in every crate using Trussed. Actually, it would...

Adding to the two suggestions in the initial post, I would now also remove all re-exports from `trussed-core`. I added them to make the migration as smooth as possible. But...

A potential workaround would be to cache the latest known release and then use [conditional requests](https://docs.github.com/en/rest/using-the-rest-api/best-practices-for-using-the-rest-api?apiVersion=2022-11-28#use-conditional-requests-if-appropriate) to check for new releases.

I think this is a misunderstanding. We almost never use rustc’s `--cfg` flag directly, just features. But in the source code, we use the `cfg` attribute to check for that...

@sosthene-nitrokey What do you think about removing the syscall implementation entirely and always returning `RequestNotAvailable`? The current implementation does not do anything anyway and it is not actually used. Then...