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

swarm: a deploy goes out only once its closure is cached and the hive has its cache facts

Browse source
This commit is contained in:
atlas 2026-11-07 11:53:25 +01:00
commit 79c1b6d81d
1 changed files with 432 additions and 92 deletions
Download patch file Download diff file Expand all files Collapse all files

8
swarm-controller/src/cache_miss.rs
View file

@ -12,10 +12,10 @@
//! refused token is "cannot tell" and rebuilds nothing.
//!
//! A record from the head with `cached` false (the builder's push failed, or the
//! cache or its token was not up yet) is not a hive's to use, and nothing else
//! pushes it before `internal/meta` moves. The pass sends its build without
//! asking the cache, and the record is rewritten with `cached` true once the
//! push lands.
//! cache or its token was not up yet) is not a hive's to use. The meta timer
//! builds its failed `BuildMeta` again, but only from the in-memory job graph, so
//! a record that outlives a restart has no retry. The pass sends its build
//! without asking the cache, and the push rewrites the record with `cached` true.
//!
//! A pass sends at most [`MAX_REBUILDS_PER_PASS`] builds, one after the other.
//! An agent whose rebuild failed, or built without pushing, is left alone for