summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* put remake content into blobstv4 days15-79/+319
|
* add chunked download and use it during rejointv4 days15-3/+844
|
* allow unsetting config optionstv4 days2-46/+264
|
* add API and CLI to print effective configtv4 days4-2/+106
|
* add configuration filestv4 days5-107/+1262
|
* wire up --mycelium-tcp-listen-porttv4 days1-2/+5
| | | | | It wasn't used before, causing the supervised daemon to always pick a random one.
* cleanup Cargo.tomltv4 days1-2/+2
|
* introduce majority voting on remakestv4 days7-95/+406
|
* add electoratetv4 days3-8/+109
| | | | | For an upcoming change in remake coordination, nodes now maintain their self-assessed liveness in the document.
* aliases are not in logs (fixup)tv4 days2-2/+2
|
* measure document saved-size only after changestv4 days2-18/+43
|
* allow import remake using the raw documenttv4 days1-6/+85
|
* add the import kind of remaketv4 days3-49/+200
|
* add endpoint to export the documenttv4 days3-0/+88
| | | | GET /admin/document to retrieve the automerge document.
* add node aliasestv4 days6-11/+147
|
* expose stats for prometheus to scrapetv4 days2-7/+514
|
* add throughput statstv4 days8-2/+231
|
* add propagation statstv4 days4-1/+126
|
* add per peer incident statstv4 days4-4/+52
|
* expose stats via the APItv4 days2-0/+136
| | | | GET /admin/stats to retrieve all stats.
* add swarm statstv4 days9-1/+238
|
* add traffic countertv4 days9-12/+270
| | | | | | | | | | 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.
* nodes prefer stable neighbourstv4 days1-10/+89
|
* assess swarm stabilitytv4 days8-11/+330
|
* add tokio-console feature (fixup)tv4 days1-1/+4
|
* edition = "2024" (fixup)tv4 days1-1/+1
|
* record RTT sampling instanttv4 days4-30/+104
|
* prefer closer sources to catch uptv4 days3-3/+49
|
* record RTT from keepalive messagestv4 days7-20/+148
|
* pull missing changestv4 days7-5/+162
| | | | | | 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 days3-55/+162
|
* sync with neighbourstv4 days6-4/+171
|
* add neighbour graphtv4 days2-0/+180
|
* add member registrytv4 days4-1/+73
|
* use nonce in handshaketv4 days5-2/+39
| | | | | 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.
* drain queued messages on startuptv4 days1-2/+48
|
* consolidate backoff codetv4 days4-49/+99
|
* retry using fresh messagestv4 days3-170/+180
| | | | | 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 days2-82/+21
| | | | | | 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.
* no heal during catch-uptv5 days1-1/+6
|
* peers that just became ready get syncstv5 days1-0/+9
| | | | | | When keepalive says ready and we didn't have taht on record before, the peer is queued for sync. Hello and hello reply don't do this because the handshake already queues a sync.
* both sides may open sync after resettv5 days6-163/+64
| | | | | | | | | | 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 days6-85/+74
|
* drop pre-membership sync messagestv5 days4-47/+10
| | | | | The handshake resets the session anyway, and the sender's reply timeout resends what still matters.
* bump number of heads in keepalive messagestv5 days5-11/+94
| | | | | 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 days4-109/+28
| | | | This allows changing sources without the fixed 30 s stall duration.
* enrich keepalive contenttv5 days5-44/+307
| | | | | | | 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 days4-11/+65
| | | | | | 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.
generated by cgit v1.3.1 (git 2.54.0) at 2026-10-28 12:20:34 +0000