Daniel Abramov

> The complexity involved in workspaces, out-of-path-builds, cargo's configuration and so on could only be represented by actually using cargo's API. This would, however, add a lot of complexity to...

> These appear to be network timeouts, are you behind a proxy? No proxy set up. Just a regular Wi-Fi connection to my router (which in turn receives the IP...

No, no special configuration. I've installed `rustup` a couple days ago (also without any special configuration) and just fetched the `cargo-outdated` from GitHub with a regular `git clone`. `cargo update...

I'm wondering if the issue may be caused by an executable not trying to fetch using all available IP addresses for a given host. Could it be that the tool...

I tried with debug logs, but I had the same experience @cmdln had: it worked without any issues on smaller repositories. Now I'm getting a slightly different error by the...

For most of the (smaller) repositories which did not work with `cargo-outdated` and triggered the errors I mentioned in my previous comments it works well now, thanks! But the bigger...

On Mac OS X I also don't have any issues, that's why I suspected the handling of IPv4/IPv6 addresses or something like this (see https://github.com/kbknapp/cargo-outdated/issues/212#issuecomment-600326277). The issue is reproducible on...

@SSheldon the issue affected the project on which I work in the company, I spot the issue and fixed it (the fix was trivial after I checked the repository, changelog...

Sounds like a good idea! By the way, that would probably solve https://github.com/burtonageo/cargo-bundle/issues/25 for Debian, as the current implementation of deb package generation in `cargo-bundle` does not seem to look...

> The feasibility of replacing google libwebrtc with webrtc-rs, These are big ambitions, I like it 🙂 I think it would be really cool to have a "native Rust" replacement...