Weihang Lo
Weihang Lo
> Workaround seems to be to set `CARGO_HTTP_MULTIPLEXING=false`. Cargo already has some built-in workaround for disabling multiplexing under some circumstances. Like [this](https://github.com/rust-lang/cargo/blob/47c911e9e6f6461f90ce19142031fe16876a3b95/src/cargo/util/network/mod.rs?plain=1#L54-L82) and [this](https://github.com/rust-lang/cargo/blob/47c911e9e6f6461f90ce19142031fe16876a3b95/src/cargo/util/context/mod.rs?plain=1#L3117-L3143). However, due to the unusual interaction...
The aforementioned patch looks like this: https://github.com/rust-lang/cargo/blob/47c911e9e6f6461f90ce19142031fe16876a3b95/src/cargo/util/context/mod.rs?plain=1#L3117-L3143 We could do stuff once we know the pattern of the failure. (sorry I don't have those machines so can only rely on...
> > This environment could also be set to show more useful debugging info: > > ``` > > CARGO_HTTP_DEBUG=true CARGO_LOG=cargo::ops::registry=debug cargo fetch > > ``` > > I don't...
> Therefore this PR is blocked on enough time having passed to being able to unconditional apply to new logic. * Do we have any discussion of “enough time” elsewhere...
> By the way, it may be related to question #10358 & #12434. Hmm… I don't quite think so. It is related to cargo's own dep-info file failed to track...
Note: #13596 was an attempt of addressing this issue. In that PR, maintainers expected that kind of environment variable detection to be in the fingerprint code, where Cargo's dep-info logic...
#14154 is another case that Cargo's depinfo strips internal set environment variables (such as `CARGO_PKG_README`) causing the rebuild detection failure.
@linyihai That seems worth a try! For #14154 we could reopen if a fix doesn't cover it.
Hmm… missing some commits. Wait a sec.
> > Provide API for people to generate different versions of lockfiles. > > @weihanglo it already supports this. `Lockfile::version` is consulted at serialization time and used to generate different...