aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* unify peers snapshot logictv9 days6-52/+24
|
* unify lock logictv9 days25-134/+116
|
* move protocol paths to dedicated moduletv9 days11-62/+96
|
* replace shadow types by wire codectv9 days3-428/+433
|
* refresh peers after stalltv9 days3-1/+57
|
* split state moduletv9 days7-1297/+1362
|
* make test RNG configurable via envtv9 days1-3/+12
|
* add replay testtv9 days1-0/+65
|
* add heads summary testtv9 days1-0/+37
|
* add random swarms testtv9 days4-32/+149
|
* add soak testtv9 days2-0/+102
|
* add clock moduletv9 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 testtv9 days2-3/+46
|
* avoid stalled sourcetv9 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_limittv9 days3-7/+16
|
* add convergence over lossy-links testtv9 days1-0/+33
|
* make sync reply timeout part of timingtv9 days4-16/+42
| | | | This enables upcoming lossy-links tests.
* recompute neighbours whenever topology changestv9 days6-5/+47
|
* run peer worker when becoming readytv9 days1-0/+8
|
* newly added neighbour get a sync attempttv9 days1-3/+12
|
* add simulation testtv9 days7-8/+976
|
* build node in separate moduletv9 days2-110/+199
|
* fix warning about swarm key (fixup)tv9 days1-1/+1
|
* require catch-up source to make progresstv9 days3-1/+98
|
* late messages don't flip peer's epoch backtv9 days7-25/+129
|
* bump abort margin & allow aborting active remaketv9 days3-42/+179
|
* build_genesis -> remake_genesis (fixup)tv9 days3-3/+3
|
* only keep list of actor IDs within one epoch (fixup)tv9 days3-2/+14
|
* allow to remake genesistv9 days5-1/+75
|
* allow to persist documenttv9 days9-84/+670
|
* nodes keep list of every actor ID they've usedtv9 days6-20/+56
|
* explain that changes get replayed by all nodes (fixup)tv9 days1-2/+2
|
* add template importer to configtv9 days1-6/+107
|
* add force module usable by API and CLItv9 days5-54/+121
|
* add files module to consistently track statstv9 days8-143/+268
|
* warn about unresolvable seeds once; log successtv9 days1-7/+22
|
* genesis conflicts seeds or recover-fromtv9 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 statstv9 days6-27/+138
|
* add possibility to start with a documenttv9 days4-13/+163
| | | | The --recover-from option allows a node start with a given document.
* add state filetv10 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 documenttv10 days4-6/+27
|
* add genesis flag and never give uptv10 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.
* compact remake fixes base at the committv10 days5-40/+138
| | | | | | | Instead of fixing base heads at when proposed, compact fixes them when committing. This shrinks the window where writes can be lost if their author restarts to the switch delay; during replace and import remakes writes can still be lost during the voting period.
* fix wording around swarm key admissiontv10 days2-3/+3
|
* allow superseding expired remakestv10 days4-26/+279
|
* remake coordinators resume after restarttv10 days3-5/+49
|
* don't commit expired remakestv10 days1-58/+93
|
* add votes registertv10 days8-124/+507
|
* bound stable-hub degreetv10 days1-4/+46
| | | | | | Each stable member can be preferred at most by 4*k members. The budget is spent in key order, which is the same on every node, so the graph stays deterministic, symmetric and connected.
* coalesce announcementstv10 days3-2/+60
|