summaryrefslogtreecommitdiffstats
path: root/src/state.rs
Commit message (Collapse)AuthorAgeFilesLines
* allow to persist documenttv3 days1-0/+2
|
* add files module to consistently track statstv3 days1-0/+2
|
* add state filetv3 days1-0/+2
| | | | | This allows storing the swarm ID and additionally discovered seeds, which prevents a formerly genesis node to start a new document.
* fix wording around swarm key admissiontv4 days1-2/+2
|
* coalesce announcementstv4 days1-0/+3
|
* cache headstv4 days1-13/+20
| | | | To reduce the number of write locks, heads are now cached.
* follow and download from ready members onlytv4 days1-2/+6
|
* only protocol-writers may modify _continuumtv4 days1-0/+3
|
* put remake content into blobstv4 days1-8/+20
|
* add chunked download and use it during rejointv4 days1-0/+24
|
* add API and CLI to print effective configtv4 days1-0/+3
|
* introduce majority voting on remakestv4 days1-0/+4
|
* add electoratetv4 days1-0/+2
| | | | | For an upcoming change in remake coordination, nodes now maintain their self-assessed liveness in the document.
* add node aliasestv4 days1-0/+2
|
* add throughput statstv4 days1-1/+14
|
* add propagation statstv4 days1-1/+6
|
* add per peer incident statstv4 days1-2/+38
|
* add swarm statstv4 days1-0/+2
|
* add traffic countertv4 days1-0/+2
| | | | | | | | | | This introduces a new wrapper that counts messages and payload bytes per peer, split by kind (hello, helloReply, sync, ping, pong), each sent, received and refused. The traffic counter goes around the firewall, which means messages dropped outbound are still counted as sent, and messages dropped inbound don't count as received.
* assess swarm stabilitytv4 days1-0/+2
|
* record RTT sampling instanttv4 days1-0/+6
|
* prefer closer sources to catch uptv4 days1-0/+6
|
* record RTT from keepalive messagestv4 days1-6/+9
|
* pull missing changestv4 days1-0/+2
| | | | | | Nodes push changes to their neighbours but don't relay them directly. In a partial mesh, nodes can learn about missing changes via keepalive messages and can pull them from their neighbours.
* find reachable neighbourstv4 days1-0/+30
|
* sync with neighbourstv4 days1-0/+18
|
* use nonce in handshaketv4 days1-0/+3
| | | | | To prevent stale hello replies to cause joins and thus stale sessions, each run gets a random ID, which used as nonce in the handshake.
* consolidate backoff codetv4 days1-20/+25
|
* retry using fresh messagestv4 days1-11/+52
| | | | | Don't store encoded messages but retry using a newly generated one. That way any accumulated changes can be delivered at once.
* heal from noticed divergencetv4 days1-6/+27
| | | | | Wait 2*keepalive but at least 20 s to trigger resync so that lost messages can be resent first.
* heal after reply timeouttv5 days1-0/+3
|
* drop stall breaker; resend needed changestv5 days1-17/+0
| | | | | | The stall breaker was superseded by regular re-handshaking Re-handshaking also gets triggered, when a node needs some of the heads its peer believes it has already sent. In that case the peer now resends what's needed.
* both sides may open sync after resettv5 days1-121/+26
| | | | | | | | | | Ready nodes will leave the first message to the pear that isn't ready. Hello and hello reply now carry ready, so readiness is known from the very first contact, before any sync. Together with the sync messages and keepalives, reports_ready is always current. After epoch switch, pings go to everyone except ready members already on the new epoch, these learn from the lagging peer's opening.
* perform handshake in one round triptv5 days1-5/+0
|
* drop pre-membership sync messagestv5 days1-4/+0
| | | | | The handshake resets the session anyway, and the sender's reply timeout resends what still matters.
* bump number of heads in keepalive messagestv5 days1-0/+4
| | | | | Instead of arbitrarily limiting the number to 16, allow filling keepalive messages as long as they don't cause mycelium to chunk it.
* probe sync source during catch-uptv5 days1-3/+14
| | | | This allows changing sources without the fixed 30 s stall duration.
* enrich keepalive contenttv5 days1-5/+9
| | | | | | | Add ready and syncs_with_you flags as well as actual heads, so the peer - ready: same meaning as in the sync message - syncs_with_you: sender counts recipient as member and in same epoch - heads: allows to tell who's behind or if both sides have changes
* use only ready peers as sync sourcetv5 days1-0/+4
| | | | | | Sync messages now carries a ready flag, telling whether the sending peer itself is joined or is itself still (re-)joining. In the latter case, the peer won't be used as sync source.
* catch up with a single source onlytv5 days1-0/+15
|
* introduce announce opening varianttv5 days1-6/+14
| | | | | This prevents a fall back to the 3 s grace period if a reset happens between the epoch switch and our opening went out.
* record the cause that started a sync sessiontv5 days1-6/+59
|
* merge sync_reset_at and epoch_unannounced into openingtv5 days1-47/+64
|
* introduce sync sessiontv5 days1-81/+90
| | | | SyncSession holds all fields that get reset by reset_sync()
* merge membership and authenticate into standingtv5 days1-13/+27
|
* announce epochs by sync instead of pingtv5 days1-4/+29
|
* pick pair leader by hash instead of key ordertv5 days1-2/+2
|
* ping only from one sidetv5 days1-2/+20
|
* open sync only from one sidetv5 days1-0/+24
| | | | | | | | | If both sides open, the openings cross, and an empty node's answer to the other opening (empty heads) makes the other side send the whole document a second time. Now after a sync reset, only the side with the smaller public key opens the sync; the other answers it, or opens itself if nothing arrives.
* don't resend sync messages to up-to-date peerstv6 days1-0/+6
| | | | | | | | | | | When an sync messages arrives and automerge has nothing to say about it, then no reply is generated. With c9279e4 it was assumed that every sync message gets an answer, so missing replies caused unnecessary resends. Now a reply is only awaited if the peer's last reported heads differ from ours. If the peer's heads become equal through a third peer without replying, the waiting will also abort if a ping or pong showss the same heads digest on both sides.
generated by cgit v1.3.1 (git 2.54.0) at 2026-10-28 11:15:17 +0000