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. |
||
|---|---|---|
| .. | ||
| app | ||
| gen | ||
| lib | ||
| mar | ||
| sur | ||
| sys | ||
| ted | ||
| tests | ||
| .gitattributes | ||
| .ignore | ||
| desk.bill | ||
| LICENSE.txt | ||
| README.md | ||
| sys.kelvin | ||
| TESTING.udon | ||
Arvo
A clean-slate operating system.
Usage
To run Arvo, you'll need Urbit. To install Urbit and run Arvo please follow the instructions in the getting started docs. You'll be on the live network in a few minutes.
If you're doing development on Arvo, keep reading.
Documentation
Find Arvo's documentation on urbit.org.
Development
To boot a fake ship from your development files, run urbit with the following arguments:
urbit -F zod -A /path/to/arvo -c fakezod
Mount Arvo's filesystem allows you to update its contents through Unix. To do so, run |mount in dojo. It is most common to |mount /=base=.
To create a custom pill (bootstrapping object) from the files loaded into the base desk, run .my/pill +solid. Your pill will appear in /path/to/fakezod/.urb/put/my.pill.
To boot a fake ship with a custom pill, use the -B flag:
urbit -F zod -A /path/to/arvo -B /path/to.pill -c fakezod
To run all tests in /tests, run -test %/tests in dojo. To run only the tests in /tests/some/path, use -test %/tests/some/path.
Maintainers
Most parts of Arvo have dedicated maintainers.
/sys/hoon: @pilfer-pandex (~pilfer-pandex)/sys/zuse: @pilfer-pandex (~pilfer-pandex)/sys/arvo: @joemfb (~master-morzod)/sys/vane/ames: @belisarius222 (~rovnys-ricfer) & @philipcmonk (~wicdev-wisryt)/sys/vane/behn: @belisarius222 (~rovnys-ricfer)/sys/vane/clay: @philipcmonk (~wicdev-wisryt) & @belisarius222 (~rovnys-ricfer)/sys/vane/dill: @fang- (~palfun-foslup)/sys/vane/eyre: @fang- (~palfun-foslup)/sys/vane/gall: @philipcmonk (~wicdev-wisryt)/sys/vane/jael: @fang- (~palfun-foslup) & @philipcmonk (~wicdev-wisryt)/app/acme: @joemfb (~master-morzod)/app/dns: @joemfb (~master-morzod)/app/aqua: @philipcmonk (~wicdev-wisryt)/app/hood: @belisarius222 (~rovnys-ricfer)/lib/hood/drum: @fang- (~palfun-foslup)/lib/hood/kiln: @philipcmonk (~wicdev-wisryt)
Contributing
Contributions of any form are more than welcome! Please take a look at our contributing guidelines for details on our git practices, coding styles, how we manage issues, and so on.
You might also be interested in:
- joining the urbit-dev mailing list.
- applying to Hoon School, a course we run to teach the Hoon programming language and Urbit application development.