| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Picked where the path goes, rustc 1.95 takes the pick's type from that place, a slice
of strings, and refuses the paths offered: picked by itself, as `rng.pick(&KEYS)` is,
it is one of the paths, which goes where a slice of strings does.
|
| |
|
|
|
|
| |
The closed paths a generated write picks one of are an array of their own, and the
events a node put a slice: picked from an array written in place, a path's type is
left to be inferred from where it goes, which some compilers don't.
|
| |
|
|
|
|
|
|
|
| |
Three nodes write at random: events at their IDs, larger than the fold allows or not,
again, or at other keys; strings and maps under the events; deletions; their entries
or others'; and what is closed. Each now and then catches up with a node that takes
their changes as it receives them (`screen::apply_bytes`). What it takes leaves at
every key under `_continuum/events` the bytes whose ID it is, the root's among them;
its document saves and loads; and another node, given all it took, takes it all.
|
| |
|
|
|
|
|
|
|
| |
Each row of `docs/store.md`, Attacks, marked unit has its test,
`store_attack_<row>`: where it is judged (`access::holding`, `access::token`), where
the store held in memory meets it (`federation::store::memory`), and where a node reads
its store from its document (`federation::held`). Tests that checked a row already take
its name; a check reads the doc's rows and fails on a unit row without its test, but for
rows 21 and 22, which the remakes bring.
|
| |
|
|
|
|
| |
Automerge writes no put of the value a key holds already, so the test can't have a node
write one: it judges such a change made by hand, a put of the event's bytes at its key,
at a history holding it.
|
|
|
Every node judges a change of a swarm holding a store by what it writes, at its history
(`docs/store.md`, What a change writes), in place of rules by path: `access::holding`.
It writes events, each at `_continuum/events/<ID>` the bytes whose SHA-256 that is, no
larger than the fold allows (the federation's 256 KiB), at a key held nowhere at the
change's history; and its node's entry, with the member list's map where there is none.
Everything else is refused, as closed: values outside `_continuum`, the policy, the
swarm's ID, users, bans, the topology, remakes and their acks. Nothing deletes or
replaces an event. A change names its node; the genesis change's writer names none, so
no change under it is taken but the genesis change.
In a swarm not holding a store, a change writing a policy naming one is refused: a swarm
holds a store from its genesis change, or not at all.
The inspector tells a put of bytes apart (`Action::PutBytes`), with the bytes, for the
events' check. All of it behind the `federation` feature.
|