-
**Requested feature**
We should check in Cargo.lock files to enable repeatable builds
**Motivation**
We've had a number of problems arise because dependencies were updated that broke our build proc…
-
**Description**
Currently, from what I gather, we either implement our own `Error` type or throw a `std::io::Error`. In general, I'm a fan of having the least external dependencies as possible and I …
-
Added as part of the [SIMD work](https://github.com/rust-lang/rfcs/pull/1199), supports feature detection based on e.g. target processor. This issue tracks stabilization.
### Relevant issues and bu…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
### Current Behaviour
Hi,
I am tryi…
-
## Problem
We're now (or about to be) facing a similar situation on the client side (`pcli`) as we were in `pd` prior to #488: we started with code designed to be an MVP, it's been extended beyond …
-
Since last rust-analyzer I get unresolved import errors on every import of names from std, such as:
```
use std::{f64::consts::FRAC_PI_2, time::Duration};
```
I noticed this error is also trig…
-
We should use proper upstream releases of all the crates that we're currently pulling in via git `rev=` dependencies. Of course, that requires actually _making_ upstream releases first...
- [x] Pub…
-
**Describe the bug**
Kernel fails to remap a PCI bridge that has no upstream. I have an Nvidia GPU which supports "MIG", aka multi-instance groups. Unlike the other GPU VFIO report, my NVIDIA GPU sup…
sdake updated
2 years ago
-
There seems to be a significant compile time regression when using the LVI mitigation passes on some crates. The smallest case I could come up with is:
```rust
#[macro_use] extern crate crunchy;
…
-
Fails with the rust integration tests:
```
$ ENARX_BACKEND=sgx RUSTFLAGS='-C target-cpu=x86-64-v4' cargo test
[…]
test echo ... FAILED
test memory_stress_test ... FAILED
test rust_sev_attestatio…