Ivan Mironov

There is a `client: reconnect` command in the command palette (Ctrl-Shift-P). Usually works for me. Automatic reconnect would definitely be nice to have though.

Seems to be fixed. At least for me, Zed was always connected for almost a week without the need to manually reconnect.

It looks like cargo currently does not support this: * https://github.com/rust-lang/cargo/issues/10310 * https://github.com/rust-lang/cargo/pull/13271

I was able to use `cargo vendor` with patched cargo: https://github.com/im-0/cargo/commit/c8524ebd42621131a6b776a69286c52f81f27c19 (this is just a https://github.com/rust-lang/cargo/pull/13271 but rebased on current `cargo` master).

@probably-neb I use `cargo vendor` when building [my own RPM packages for Fedora](https://github.com/im-0/fedora-rpm.zed). Builders on [copr](https://copr.fedorainfracloud.org/) are isolated from any network by default, thus `cargo` is unable to download any...

@PedroHLC are you 100% sure that you can not use patched cargo? Patch is needed solely for `cargo vendor`. Then you can use normal unpatched cargo for `cargo build`.

@P1n3appl3 `--no-merge-sources` is enough for me currently. However I would prefer to have this fixed in Zed. Currently Zed uses two slightly different copies of `reqwest` and this does not...

If you decide to merge this PR, please merge it without squashing into a single commit. Single commit will make benchmarking before/after changes much more difficult.

I asked my friends to run the same benchmarks on other CPUs (preferably Intel) and got some interesting results. It turned out that some benchmarks regressed and some improved on...

Done! Still requires Simba with https://github.com/dimforge/simba/pull/76