ilyakooo0/urbit
1
0
Fork 0
mirror of https://github.com/ilyakooo0/urbit.git synced 2024-12-14 17:41:33 +03:00
Code Issues Packages Projects Releases Wiki Activity
An operating function
18,114 Commits 6 Branches 0 Tags 164 MiB
hoon 79.3%
TypeScript 16.7%
JavaScript 2.3%
CSS 0.4%
Python 0.4%
Other 0.8%
7d7f4133a6
Go to file
Philip Monk 7d7f4133a6
arvo: add bar stack to hoon stack trace 
We have three stacks: the hoon stack, bar stack, and duct stack.  This
turns the bar stack to a list of ducts and adds it to the hoon stack.
This tells you the ducts of the moves that caused the move where you
crashed.

See:

recover: dig: intr
crud: %belt event failed
bail: intr
  bar-stack
~[
  ~[/g/use/spider/~zod/build/~.dojo_0v5ogno.5anji.vn3f6.4gs7t.6r2ft /d //term/1]
  ~[/d //term/1]
  ~[/g/use/spider/~zod/find/~.dojo_0v5ogno.5anji.vn3f6.4gs7t.6r2ft /d //term/1]
  ~[/g/use/dojo/~zod/out/~zod/spider/drum/wool /d //term/1]
  ~[/d //term/1]
  ~[/g/use/dojo/~zod/drum/hand /d //term/1]
  ~[/g/use/hood/~zod/out/~zod/dojo/drum/phat/~zod/dojo /d //term/1]
  ~[/d //term/1]
  ~[//term/1]
]
call: failed
/~zod/home/~2020.3.17..23.14.11..50e0/sys/vane/ford:<[6.128 3].[6.220 5]>
/~zod/home/~2020.3.17..23.14.11..50e0/sys/vane/ford:<[6.129 3].[6.220 5]>
/~zod/home/~2020.3.17..23.14.11..50e0/sys/vane/ford:<[6.132 3].[6.220 5]>
...
2020-03-17 16:31:38 -07:00
.github/ISSUE_TEMPLATE meta: os1 bug template, provide desktop os example 2020-03-13 10:28:54 +01:00
bin arvo: add bar stack to hoon stack trace 2020-03-17 16:31:38 -07:00
doc/spec Misc cleanup blocking CC-Release. (#1249) 2019-04-24 17:27:27 -07:00
extras Misc cleanup blocking CC-Release. (#1249) 2019-04-24 17:27:27 -07:00
nix build: remove urbit-large-log-limit derivation 2020-03-01 23:04:22 +04:00
pkg arvo: add bar stack to hoon stack trace 2020-03-17 16:31:38 -07:00
sh Merge branch 'jt/rename-release-tarballs' (#2395) 2020-03-05 12:22:31 +04:00
.gitattributes gitattributes: export-ignore test directories [ci skip] 2020-02-01 12:07:13 +04:00
.gitignore gitignore: re-add mystery lines [ci skip] 2020-03-01 23:19:01 +04:00
.ignore Can now |hi to King Haskell over Ames! (and merged Master) 2019-07-31 22:16:02 -07:00
.mailmap mailmap: add pkova [ci skip] 2020-01-30 15:53:19 +04:00
.stylish-haskell.yaml stylish-haskell 2019-07-12 12:27:15 -07:00
.travis.yml Update scripts to point to urbit-king. 2020-01-23 21:34:21 -08:00
CONTRIBUTING.md meta: update CONTRIBUTING, MAINTAINERS 2020-03-16 11:32:55 +04:00
default.nix Nix Build + Monorepo Structure (#1196) 2019-03-04 16:43:53 -08:00
LICENSE.txt Restore toplevel LICENSE.txt file. 2020-01-28 13:24:39 -08:00
MAINTAINERS.md meta: update CONTRIBUTING, MAINTAINERS 2020-03-16 11:32:55 +04:00
Makefile Build Linux static executables. (#2120) 2019-12-19 08:11:59 -08:00
README.md readme: update bridge URL [ci skip] 2020-01-23 04:38:27 +04:00

README.md

Urbit

A personal server operating function.

The Urbit address space, Azimuth, is now live on the Ethereum blockchain. You can find it at 0x223c067f8cf28ae173ee5cafea60ca44c335fecb or azimuth.eth. Owners of Azimuth points (galaxies, stars, or planets) can view or manage them using Bridge, and can also use them to boot Arvo, the Urbit OS.

Install

To install and run Urbit, please follow the instructions at urbit.org/docs/getting-started/. You'll be on the live network in a few minutes.

If you're interested in Urbit development, keep reading.

Development

Build Status

Urbit uses Nix to manage builds. On Linux and macOS you can install Nix via:

curl https://nixos.org/nix/install | sh

The Makefile in the project's root directory contains useful phony targets for building, installing, testing, and so on. You can use it to avoid dealing with Nix explicitly.

To build Urbit, for example, use:

make build

The test suite can similarly be run via a simple:

make test

Note that some of the Makefile targets need access to pills tracked via git LFS, so you'll also need to have those available locally:

git lfs install
git lfs pull

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: