7494bf57c6
When merging, +reachable-takos is called roughly once per merge commit in the ancestry of the new commit. +reachable-takos was exponential in the number of merge commits in the ancestry of the commit it's looking at, due to mishandling of the accumulator. This makes it linear. Of course, linear x linear is still quadratic, which is not great. I doubt +reachable-takos can be made asymptotically better, but +reduce-merge-points/+find-merge-points probably can. 50 merge commits already gives about 14.000 iterations through the loop in +reachable-takos. Another option is to try to memoize this somehow, but a simple ~+ is insufficient since `s` is usually different. In local tests on macOS with a -L copy of ~wicdev-wisryt, this speeds up OTAs significantly. The majority of time was spent on this. |
||
|---|---|---|
| .. | ||
| app | ||
| gen | ||
| lib | ||
| mar | ||
| ren | ||
| sur | ||
| sys | ||
| ted | ||
| tests | ||
| .gitattributes | ||
| .ignore | ||
| LICENSE.txt | ||
| README.md | ||
| 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 /=home=.
To create a custom pill (bootstrapping object) from the files loaded into the home 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 in dojo. +test /some/path would only run all tests in /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: @jtobin (~nidsut-tomdun)/sys/vane/ames: @belisarius222 (~rovnys-ricfer) & @joemfb (~master-morzod)/sys/vane/behn: @belisarius222 (~rovnys-ricfer)/sys/vane/clay: @philipcmonk (~wicdev-wisryt)/sys/vane/dill: @bernardodelaplaz (~rigdyn-sondur)/sys/vane/eyre: @eglaysher (~littel-ponnys)/sys/vane/ford: @belisarius222 (~rovnys-ricfer) & @eglaysher (~littel-ponnys)/sys/vane/gall: @jtobin (~nidsut-tomdun)/sys/vane/jael: @fang- (~palfun-foslup) & @joemfb (~master-morzod)/app/acme: @joemfb (~master-morzod)/app/dns: @joemfb (~master-morzod)/app/hall: @fang- (~palfun-foslup)/app/talk: @fang- (~palfun-foslup)/app/aqua: @philipcmonk (~wicdev-wisryt)/lib/test: @eglaysher (~littel-ponnys)
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.