aboutsummaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
...
* remove unit suffixes from fieldstv10 days4-34/+61
|
* allow humand-friendly durations and sizes in CLItv10 days9-67/+341
|
* unify API error responsestv10 days3-17/+62
|
* SyncSessions owns Automerge's sync statetv10 days5-85/+128
|
* cleanup mycelium daemontv10 days4-53/+21
|
* split mycelium daemon in its own moduletv10 days4-368/+376
|
* unify keepalivetv10 days1-15/+23
|
* split peer moduletv10 days9-915/+995
|
* unify peers snapshot logictv10 days6-52/+24
|
* unify lock logictv10 days25-134/+116
|
* move protocol paths to dedicated moduletv10 days11-62/+96
|
* replace shadow types by wire codectv11 days3-428/+433
|
* refresh peers after stalltv11 days3-1/+57
|
* split state moduletv11 days7-1297/+1362
|
* make test RNG configurable via envtv11 days1-3/+12
|
* add replay testtv11 days1-0/+65
|
* add heads summary testtv11 days1-0/+37
|
* add random swarms testtv11 days4-32/+149
|
* add soak testtv11 days2-0/+102
|
* add clock moduletv11 days18-75/+164
| | | | | The Clock module is the system clock that every unix timestamp new goes through. It comes with an offset that only tests can set.
* add stalled source testtv11 days2-3/+46
|
* avoid stalled sourcetv11 days3-2/+28
| | | | | | | | | | | | | A source given up for not answering our sync messages could become the source again straight away. Whoever asks first after the reset takes the role, and that's often the same peer, which would then stall for another delivery limit. Now, a stalled source isn't chosen again for one more delivery_limit. If it's the only candidate, catching up waits that long and then tries it again. Before, a retry with that peer couldn't have helped any sooner anyway: a source is only given up after a whole delivery limit without a sync message, and that clock restarts when it is chosen again.
* MYCELIUM_DELIVERY_LIMIT -> Timing::delivery_limittv11 days3-7/+16
|
* add convergence over lossy-links testtv11 days1-0/+33
|
* make sync reply timeout part of timingtv11 days4-16/+42
| | | | This enables upcoming lossy-links tests.
* recompute neighbours whenever topology changestv11 days6-5/+47
|
* run peer worker when becoming readytv11 days1-0/+8
|
* newly added neighbour get a sync attempttv11 days1-3/+12
|
* add simulation testtv11 days7-8/+976
|
* build node in separate moduletv11 days2-110/+199
|
* fix warning about swarm key (fixup)tv11 days1-1/+1
|
* require catch-up source to make progresstv11 days3-1/+98
|
* late messages don't flip peer's epoch backtv11 days7-25/+129
|
* bump abort margin & allow aborting active remaketv11 days3-42/+179
|
* build_genesis -> remake_genesis (fixup)tv11 days3-3/+3
|
* only keep list of actor IDs within one epoch (fixup)tv11 days3-2/+14
|
* allow to remake genesistv11 days5-1/+75
|
* allow to persist documenttv11 days9-84/+670
|
* nodes keep list of every actor ID they've usedtv11 days6-20/+56
|
* explain that changes get replayed by all nodes (fixup)tv11 days1-2/+2
|
* add template importer to configtv11 days1-6/+107
|
* add force module usable by API and CLItv11 days5-54/+121
|
* add files module to consistently track statstv11 days8-143/+268
|
* warn about unresolvable seeds once; log successtv11 days1-7/+22
|
* genesis conflicts seeds or recover-fromtv11 days1-16/+19
| | | | | genesis together with seeds or recover-from is now an error wherever the values come from, and not settled by precedence.
* add disk I/O statstv11 days6-27/+138
|
* add possibility to start with a documenttv11 days4-13/+163
| | | | The --recover-from option allows a node start with a given document.
* add state filetv11 days7-4/+266
| | | | | This allows storing the swarm ID and additionally discovered seeds, which prevents a formerly genesis node to start a new document.
* put swarm ID into the documenttv11 days4-6/+27
|
* add genesis flag and never give uptv11 days3-76/+112
| | | | | | | | | The --genesis flag has been introduced to start with a new document. This prevents restarts to accidentally start with a new document and accept reads/writes, causing a second swarm to appear. Additionally, bootstrapping doesn't timeout anymore as that's of no use for nobody.