mara/hyperhive
mara/hyperhive
Watch
0
0
Fork
You've already forked hyperhive
 0
Code Activity

archetype flows on the board list the agents the router sends to, and the docs say a switch-off key outlives its flow

Browse source
This commit is contained in:
atlas 2026-11-11 20:45:07 +01:00 • committed by mara
commit 13ff33ead0
1 changed files with 66 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

4
swarm-queue-client/Cargo.toml
View file

@ -16,7 +16,7 @@ edition.workspace = true
# client; the exception exists because an agreement between two crates has
# to live in one of them, and neither end of that bucket is senior to the
# other.
kv = ["async-nats/kv"]
kv = ["async-nats/kv", "dep:futures-util"]
# 🩸 `jetstream` is NOT in async-nats's default feature set here — the
# workspace-level dependency turns default features off entirely (see
# root `Cargo.toml`: `server_2_14`/`nkeys`/`ring` only). `kv` above works
@ -83,6 +83,8 @@ router-todo = ["async-nats/jetstream"]
# above - the connect itself needs none of them.
async-nats.workspace = true
hive-types = { workspace = true, optional = true }
# `agent_status::roster` collects the stream's subject listing.
futures-util = { workspace = true, optional = true }
# `blocking` on top of the workspace default (`form`/`json`/`rustls`) —
# `mint_token_for_blocking` needs `reqwest::blocking::Client` for a caller
# with no tokio reactor to `.await` an async request on (an OTLP exporter's