Robin Krahl
Robin Krahl
I ran into this issue when trying to use both `littlefs2-sys` and `nettle-sys` in the same crate. example Cargo.toml ``` [package] name = "bindgen-test" version = "0.1.0" edition = "2021"...
Also, if this isn’t fixed in the code, it should at least be documented to make users aware of this issue and how to fix it.
Thank you for the PR! I did not have a closer look yet but I just want to give you a heads-up that we are already working on a solution...
@alt3r-3go https://github.com/trussed-dev/trussed/pull/31 refactors the client used for the tests and should allow you to execute them normally with `cargo test --features virt`.
Will be Is fixed by https://github.com/solokeys/solo2/pull/122.
I tried to reproduce the problem with usbip over the network with a non-Qubes OS but everything worked fine in this setup (both machines using Linux 6.1.76).
It is not necessary, but I think it has multiple benefits: It leads to simpler code. It allows us to get rid of the unnecessary `Fs` type that is just...
What kind of integration tests would you like to add? Generally, I think it would make sense to split the code into the unsafe C API that just does the...
Maybe the change to `C_Initialize`/`C_Finalize` I suggested in that PR would already be enough for testing that? I’m not opposed to splitting the crate, but as it adds additional release...
Would that be an issue? I think if we really want integration tests for a library with a global state, we need sequential tests. If you only want to test...