It is possible for a pair of nodes to concurrently ask each other to fetch some repo. These "crossing" requests are problematic, because the nodes end up waiting for each other to reply, and the reply never comes. With this change, the node pair agrees on proceeding with one of the fetches, while canceling the other. |
||
|---|---|---|
| .github/workflows | ||
| .nix | ||
| radicle | ||
| radicle-cli | ||
| radicle-cli-test | ||
| radicle-cob | ||
| radicle-crdt | ||
| radicle-crypto | ||
| radicle-dag | ||
| radicle-httpd | ||
| radicle-node | ||
| radicle-remote-helper | ||
| radicle-ssh | ||
| radicle-term | ||
| radicle-tools | ||
| .dockerignore | ||
| .env.seed | ||
| .gitignore | ||
| CONTRIBUTING.md | ||
| Cargo.lock | ||
| Cargo.toml | ||
| DCO | ||
| LICENSE-APACHE | ||
| LICENSE-MIT | ||
| README.md | ||
| build.rs | ||
| docker-compose.yml | ||
| rust-toolchain | ||
README.md
❤️🪵
Radicle Heartwood Protocol & Stack
Heartwood is in the early development phase and is not yet ready for use.
Installation
# Command line tools
$ cargo install --locked --path ./radicle-cli
# The radicle node
$ cargo install --locked --path ./radicle-node
# Git tool to support the 'rad://' remote scheme
$ cargo install --locked --path ./radicle-remote-helper