Block a user
Store the routing table in the database (part of #122)
Store the routing table in the database (part of #122)
PASS: both findings of the first review (sneak/routewatch#186 (comment)) are fixed, and nothing else blocks the merge into next.
- Judgement call: I took…
Store the routing table in the database (part of #122)
- Fixed:
TestReadRouteTableGivesATableThatTakesLaterUpdatesapplies aWithdraw, aPeerDownof a loaded peer and anAnnounceto both tables, then compares every read. It catchesLoadnot…
fix: a zero-minimum balance check never sets the output side (closes #649)
Rework:
- Finding 1: fixed in
decode(), with a test of the first example, the check placed before and after theUNWRAP_WETH. README and the comment in that branch say so; the judgement call…
Store the routing table in the database (part of #122)
FAIL (needs-rework)
- No test covers the per-peer prefix counts on a table read back from the database.
internal/routetable/routetable.go,Load(line 249), with its tests in…
fix: a network switch in Settings leaves no balance from the previous network stored (closes #653)
Rework of sneak/AutistMask#689 (comment):
- Fixed: the switch is now made on the stored record, and the page copies the switched fields from it, so the token…
TestIntegrationKill sometimes times out waiting for the killed user's QUIT
internal/handlers tests take about 26 seconds, over the 20-second target
Run the internal/handlers tests in parallel (closes #194)
Run the internal/handlers tests in parallel (closes #194)
PASS: the internal/handlers tests now run in parallel, one lock covers every use of the global viper instance, each test still has its own server and database, and the package is well under the…
fix: a zero-minimum balance check never sets the output side (closes #649)
Review: FAIL (needs-rework)
decode()insrc/shared/uniswap.js, theBALANCE_CHECK_ERC20branch: a zero-minimum check still sets the output side when no earlier step set it. The check…
Keep the whole routing table in memory and in one database table, pruning only redundant routes so it stays bounded
Step 2, the routing table in the database, is up for review in sneak/routewatch#186. Nothing uses it yet.
Two figures for the later steps: reading a full table at…
Store the routing table in the database (part of #122)