Nathan Sobo 17c9aa1819 Remove ShareWorktree message ... Instead, create an empty worktree on guests when a worktree is first *registered*, then update it via an initial UpdateWorktree message. This prevents the host from referencing a worktree in definition RPC responses that hasn't yet been observed by the guest. We could have waited until the entire worktree was shared, but this could take a long time, so instead we create an empty one on guests and proceed from there. We still have randomized test failures as of this commit: SEED=9519 MAX_PEERS=2 ITERATIONS=10000 OPERATIONS=7 ct -p zed-server test_random_collaboration Co-Authored-By: Max Brunsfeld <maxbrunsfeld@gmail.com> Co-Authored-By: Antonio Scandurra <me@as-cii.com>		2022-02-23 11:56:09 -07:00
..
src	Remove ShareWorktree message	2022-02-23 11:56:09 -07:00
Cargo.toml	Sign symbols so that we can trust opening buffers for them from guests	2022-02-22 18:43:16 +01:00