mirror of
https://github.com/urbit/shrub.git
synced 2024-12-21 01:41:37 +03:00
999f0e84e9
Stale lanes may cause forwarding loops. Imagine the following: 1) Planet A is live. Galaxy B, its indirect sponsor, learns of its route. 2) A goes offline. Another ship, C, is started in its place, at the same route. 3) B receives a packet for A, forwards it to the known route. 4) C received the packet, forwards it to B. 5) Repeat from 3. Here, we update the forward lane(s) scry used by the runtime to not produce a peer's lane if they haven't communicated with us in the last hour. Everyone's supposed to ping their sponsorship chain every 30 seconds. If those aren't going through, you shouldn't expect to be reachable anyway. We may or may not want to update +send-blob to match. |
||
|---|---|---|
| .. | ||
| arvo | ||
| base-dev | ||
| bitcoin | ||
| btc-wallet | ||
| docker-image | ||
| ent | ||
| garden | ||
| garden-dev | ||
| grid | ||
| herb | ||
| hs | ||
| interface | ||
| landscape | ||
| npm | ||
| urbit | ||
| urcrypt | ||
| webterm | ||
| symbolic-merge.sh | ||