urbit / arvo Goto Github PK

Home Page: https://github.com/urbit/urbit

arvo css hoon html javascript nock sail

arvo's Introduction

Urbit

Urbit is a personal server stack built from scratch. It has an identity layer (Azimuth), virtual machine (Vere), and operating system (Arvo).

A running Urbit "ship" is designed to operate with other ships peer-to-peer. Urbit is a general-purpose, peer-to-peer computer and network.

This repository contains the Arvo Kernel

For the Runtime, see Vere. For more on the identity layer, see Azimuth. To manage your Urbit identity, use Bridge.

Install

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

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, and how we manage issues.

You might also be interested in joining the urbit-dev mailing list.

Release

For details about our release process, see the maintainers guidelines

arvo's People

Contributors

Stargazers

Watchers

Forkers

ohaitch cgyarvin philipcmonk galenwp ault011 chc4 rsaarelm zaphar joemfb knubie dhaffey fang- yebyen billthebest frodwith xykj61 eglaysher theesteemedmrblowsky livweb-havweb juped hoclun-rigsep max19 deosai ovz casey ericfode mattlevan ixv mikolajpp mrdomino jfranklin9000 cxk280 xmobileio beasta famousj soros1321 tacryt-socryp bernardodelaplaz baudtack rmariani jglukasik wcable desantis stjordanis farxial-forks-collection yosoyubik splined jessicalang19 maximilianlight mckpm pkova dillon adklempner

arvo's Issues

Nest bails improperly on mistyped "span"

~zod:dojo> =+(p=%noun .*(.(p ~)|!=((~(meet ut p:!>(*span)) p))))
bail: fail

bail: 3
\ {{spins indefinitely}}

and on ^C

recover: dig: intr
intr
/~zod/home/~2016.3.11..19.18.49..0238/arvo/hoon:<[10.967 15].[10.998 57]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/hoon:<[10.968 15].[10.998 57]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/hoon:<[10.969 15].[10.998 57]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/hoon:<[10.971 15].[10.998 57]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/hoon:<[10.973 15].[10.998 57]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/hoon:<[10.973 29].[10.973 44]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/hoon:<[11.038 3].[11.043 13]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/hoon:<[11.040 3].[11.043 13]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/hoon:<[11.041 3].[11.043 13]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/hoon:<[11.042 5].[11.042 47]>
[%swim-call-vane %f %exec ~]
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.812 3].[1.856 42]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.813 3].[1.856 42]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.814 3].[1.856 42]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.842 3].[1.856 42]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.843 3].[1.856 42]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.846 3].[1.856 42]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.847 5].[1.855 7]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.852 7].[1.854 64]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.854 7].[1.854 64]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.854 12].[1.854 64]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[189 5].[195 43]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[190 5].[195 43]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[191 5].[195 43]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[192 5].[195 43]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[195 5].[195 43]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[582 7].[595 9]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[583 7].[595 9]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[584 7].[595 9]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[584 11].[584 54]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[584 15].[584 54]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.196 7].[1.197 56]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[399 7].[409 15]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[402 13].[409 9]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[402 17].[402 40]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[402 21].[402 40]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.197 32].[1.197 55]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.212 7].[1.372 9]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.213 7].[1.372 9]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.214 7].[1.372 9]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.337 9].[1.343 23]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.338 9].[1.343 23]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[399 7].[409 15]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[402 13].[409 9]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[402 17].[402 40]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[402 21].[402 40]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[482 7].[496 38]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[483 7].[496 38]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[484 9].[484 34]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[399 7].[409 15]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[402 13].[409 9]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[402 17].[402 40]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[402 21].[402 40]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.341 9].[1.343 23]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.341 19].[1.341 41]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.188 7].[1.192 32]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.189 7].[1.192 32]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[399 7].[409 15]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[402 13].[409 9]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[402 17].[402 40]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[402 21].[402 40]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.191 7].[1.192 32]>
/~zod/home/~2016.3.11..19.18.49..0238/arvo/ford:<[1.191 23].[1.191 53]>

arc should just be called sur in the dojo

If we call libraries lib then shouldn't we just call structures sur? Not sure what an arc is, and don't really feel like I need to know.

Security drivers don't check that requested identity is granted by service provider

The oauth libraries add "login hints" that select the correct variant if the user is not logged in(or logged in with multiple accounts including the intended one), but this is silently overridden if the wrong account is logged in. Correct behaviour here would be making an "inspect token" call checking that the username which provided it matches the usr parameter passed into the driver.
#73 makes this somewhat difficult in the general case

Triaged: P-low, multi-user support is largely demonstrative.

~doznec flips out needing something

  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/hoon:<[10.969 15].[11.000 57]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/hoon:<[10.970 15].[11.000 57]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/hoon:<[10.971 15].[11.000 57]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/hoon:<[10.973 15].[11.000 57]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/hoon:<[10.975 15].[11.000 57]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/hoon:<[10.975 29].[10.975 44]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/hoon:<[11.040 3].[11.045 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/hoon:<[11.042 3].[11.045 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/hoon:<[11.043 3].[11.045 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/hoon:<[11.044 5].[11.044 47]>
  [%swim-call-vane %e %west ~]
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.844 3].[1.872 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.853 3].[1.872 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.854 3].[1.872 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.864 3].[1.872 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.865 3].[1.872 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.866 3].[1.872 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.867 3].[1.872 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.868 3].[1.872 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.869 3].[1.872 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.870 3].[1.872 13]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.871 5].[1.871 63]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.871 10].[1.871 63]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[586 5].[714 7]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[587 5].[714 7]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[588 5].[714 7]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[589 5].[714 7]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[686 7].[711 9]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[687 7].[711 9]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[688 7].[711 9]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[691 7].[711 9]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[693 15].[693 61]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.447 32].[1.456 55]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.448 7].[1.456 55]>
  {}
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.449 7].[1.456 55]>
  /~doznec/home/~2016.3.15..00.43.25..4603/arvo/eyre:<[1.449 21].[1.449 40]>
  %need
kick: lost %hear on //ames

@ohAitch pls

The only thing that I can find that's different between ~doznec and anything else on the network is ~doznec having :ask running.

Callback url expects user id in path or query string

Isn't set up to handle Twitter "here, have a token at a static url, you can use it to find out what account it represents if you really care" flow.

Triaged: p-low

Login page shouldn't say "planet"

https://github.com/urbit/arvo/blob/master/arvo/eyre.hoon#L414

Galaxies and comets alike all use the same login screen.

Ford runs ++lurk unvirtualized in the ++pact mar/hoon special case.

This should just be a normal slam, |=({a/@t b/(urge cord)} (lore (lurk (role a) b))) down a vase level.
The .hoon special cases in general probably belong in %clay not ford.

The lurk crash currently observed(~2016.3.2..20.06.09) when trying to start a sub:

➤ bin/urbit -c test
~
urbit: home is test
loom: mapped 2048MB
boot: installed 215 jets
boot: loading ./urbit.pill
arvo: time: ~2016.3.2..19.56.19..ec04
generating 2048-bit RSA pair...
cp ./urbit.pill test/.urb
saving passcode in test/.urb/code.~bosmev-narsed
(for real security, write it down and delete the file...)
ames: czar zod.urbit.org: ip .192.241.195.84
ames: on localhost, UDP 65480.
http: live (insecure) on 8081
http: live ("secure") on 8444
; ~zod not responding still trying
; ~zod is ok
; ~zod is your neighbor
; ~zod is your neighbor
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/hoon:<[10.951 15].[10.982 57]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/hoon:<[10.952 15].[10.982 57]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/hoon:<[10.953 15].[10.982 57]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/hoon:<[10.955 15].[10.982 57]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/hoon:<[10.957 15].[10.982 57]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/hoon:<[10.957 29].[10.957 44]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/hoon:<[11.022 3].[11.027 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/hoon:<[11.024 3].[11.027 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/hoon:<[11.025 3].[11.027 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/hoon:<[11.026 5].[11.026 47]>
  [%swim-call-vane %f %exec ~]
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.765 3].[1.809 42]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.766 3].[1.809 42]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.767 3].[1.809 42]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.795 3].[1.809 42]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.796 3].[1.809 42]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.799 3].[1.809 42]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.800 5].[1.808 7]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.805 7].[1.807 64]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.807 7].[1.807 64]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.807 12].[1.807 64]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[182 5].[188 43]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[183 5].[188 43]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[184 5].[188 43]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[185 5].[188 43]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[188 5].[188 43]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[544 7].[557 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[545 7].[557 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[546 7].[557 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[546 11].[546 54]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[546 15].[546 54]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.158 7].[1.159 56]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[366 7].[376 15]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[369 13].[376 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[369 17].[369 40]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[369 21].[369 40]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.159 32].[1.159 55]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.174 7].[1.334 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.175 7].[1.334 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.176 7].[1.334 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.308 9].[1.320 59]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.309 15].[1.319 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.310 11].[1.319 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.311 11].[1.319 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.316 36].[1.316 56]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.309 15].[1.319 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.310 11].[1.319 13]>
  [skipped over 393 frames]
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.310 11].[1.319 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.311 11].[1.319 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.316 36].[1.316 56]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.309 15].[1.319 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.310 11].[1.319 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.311 11].[1.319 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.316 36].[1.316 56]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.309 15].[1.319 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.310 11].[1.319 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.311 11].[1.319 13]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.315 36].[1.315 64]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.315 42].[1.315 63]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.174 7].[1.334 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.175 7].[1.334 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.176 7].[1.334 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.293 9].[1.294 31]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.294 9].[1.294 31]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.675 7].[1.723 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.676 7].[1.723 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[366 7].[376 15]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[369 13].[376 9]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[369 17].[369 40]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[369 21].[369 40]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.682 43].[1.722 43]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.683 9].[1.722 43]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.684 11].[1.694 55]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.686 11].[1.694 55]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.687 11].[1.694 55]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.689 11].[1.694 55]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.690 11].[1.694 55]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.693 11].[1.694 55]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.693 15].[1.693 51]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.693 19].[1.693 51]>
  /~zod/home/~2016.2.29..22.15.58..cb54/arvo/ford:<[1.693 25].[1.693 50]>
<awaiting hood, this may take a few minutes>

Special handling of .hoon mark should move to clay

Second point of #38

%pact shouldn't be used for the first revision anyway according to @philipcmonk
%bunt, used only by %volt, can easily be special cased with a ++volt-silk arm.
%cast to not-mime only ever occurs on direct cages, and can be similarly wrapped with ++cast-cage.

The keel mutation-fail error message should be multiline

Currently crams all misnested types into one %leaf.

++mold $-(* *) is a bad example of a mold

++clam used to be, and ++mold should be, _,*. (*$-(* *) a) is 0 instead of a, making generic containers like (list) misnormalize their contents to 0, breaking constructions like ;;({(unit) (map)} foo).

sole-no generates a ~& %dy-made-dial-abort

Running +code on a fake ~zod:

%dy-made-dial-abort
> +code
wisnyx-sitnev-podwen-matzod

Just sorta confusing.

/+ b b -find-.b

Including a library from another library in ford doesn't work. CC @cgyarvin

> /+  a
> .
/~zod/home/~2016.3.7..23.44.34..6cad/arvo/ford:<[1.179 24].[1.179 52]>
/~zod/home/0/lib/a:<[1 8].[1 9]>
-find.b
ford: build failed ~[/g/~zod/use/dojo/~zod/inn/hand /g/~zod/use/hood/~zod/out/dojo/drum/phat/~zod/dojo /d //term/1]

# This is a shell archive.  Save it in a file, remove anything before
# this line, and then unpack it by entering "sh file".  Note, it may
# create directories; files and directories will be owned by you and
# have default permissions.
#
# This archive contains:
#
#   lib/a.hoon
#   lib/b.hoon
#
echo x - lib/a.hoon
sed 's/^  //' >lib/a.hoon << 'END-of-lib/a.hoon'
  /+  b  b
END-of-lib/a.hoon
echo x - lib/b.hoon
sed 's/^  //' >lib/b.hoon << 'END-of-lib/b.hoon'
  %foo
END-of-lib/b.hoon
exit

Bikeshedding: `++li`

Cc @cgyarvin
I am fond of names like weld, skim, and skip, and the %~ "method call" syntax is at present too unweildy(see #16). Additionally, things like sort, flop, scag/slag, etc. have no clear analogue in trees(except perhaps qeus?), and while this doesn't matter for the principle of |_ cores, it is a consistency of hoon/hoon interface that would be sacrificed.

Homo and limo should definitely go next to silt and milt in the constructor section, and any~li/all~li would be outright better names, but the rest are far too commonly used to move them without coming up with three-letter mnemonics that are significantly better than e.g. the average runic keyword.

Remove vestigial tap argument

I do not believe I've ever seen tap:by in any form other than (~(tap by foo)). Would anyone (@cgyarvin, @philipcmonk) mind if I added a +- all (tap) to by, in, to, and converted existing code to use it? Perhaps tap should go altogether, but that would involve (minor) mucking with jets, official deprecation, etc.

:dojo should retain buffer until request finishes

I remember at some point a crash would leave your input where it was to let you fix it, instead of accepting the input into the history.

Similarly, a blocked dojo request should show a spinner over the entered command, making it obvious why your shell is rejecting input. And perhaps accept ^C instead of backspace to cancel, @cgyarvin?

Separate type-checks for head and tail of generator arguments

Tag @ault011

Confusing:

nest-fail
-want.{{* *} {txt/@tas $~} $~}
- have
{ { now/@da
    eny/@uvI
    bec/{p/@p q/@tas r/?({$tas p/@tas} {$da p/@da} {$ud p/@ud})}
  }
  $~
  $~
}

Somewhat better:

nest-fail
-want.{{txt/@tas $~} $~}
-have.{$~ $~}

In particular, mis-called generators are a separate, common error from mis-written generators.

Add !: syntax to ford.

A !: at the top of the file should light up everything, including twigs in /~ and /;, instead of having to hunt around for which core you're in etc.
Conversely, a !. e.g. inside one horn should also work.

:examples-ping|send ~zod 'h' does not look in /gen/examples/ping/send

Please fix for me so we can keep the tutorials in a standard format :)

Take %ask generator stuff out of sole- namespace

The bottom half of sur/sole concerns dojo generators, and uses only sole-prompt from the top half.

Gall fails to type-check slams

> *%/app/err/hoon '|_  ^  ++  poke-noun  |=(a/^ ?>(.?(a) `+>.$))  --'
: /~zod/home/585/app/err/hoon
> :err ~
> |start %err
/~zod/home/0/app/err:<[1 30].[1 45]>

Give better feedback when asking a foreign ship for SSO

Let's say I started a comet, then later start a planet. When I try to log in to the planet I get stuck %asking-foreign since my cookie indicates that I'm logged in as the comet. If we gave an intermediate page with some feedback that'd be best. It should include the option to log out.

[unmerged] :twit prints a link to any successfully posted message

This is useful for demo purposes but should be replaced with getting the post back via long-poll. Or for that matter pre-loading it into the user station, but still not as a %app message.

URLs not escaped in talk

Command

~zod:talk() http://fo.ba/%20%20.ko

Expected

         ~zod/ http://fo.ba/%20%20.ko

Result

         ~zod/ http://fo.ba/  .ko

:twit .^ should have an authenitcated/unauthenticated distinction

See commented-out ++user-to-path, ++user-from-path

+moon is failing

> +moon
/~pormev-taglyn/home/~2016.2.16..21.37.07..74d7/arvo/ford:<[1.303 24].[1.303 38]>
nest-fail
-want.[[now=@da eny=@uvI bec=[p=@p q=@tas r=?([%tas p=@tas] [%da p=@da] [%ud p=@ud])]] %~]
-have.[[now=@da eny=@uvI bec=[p=@p q=@tas r=?([%tas p=@tas] [%da p=@da] [%ud p=@ud])]] %~ %~]

Ford /!mark/ should check output type

Currently, lake is used, which means that the output is molded in cases of type mismatch. This causes problems, especially when said output is accidentally a core with all of zuse+hoon in it.

Replacing /@ with a /_ argument

There used to be three horns for "/_, except only for filenames of a specific odour". Now, only /@ "by @da" remains, and it's used once in tree-comments; and a ford example using the defunct old meaning of "by @ud".

A filter arm can be added in zuse, with /@ officially becoming /; (ordered %da) /_. But the functionality is in ford is so that the non-matching paths are ignored as opposed to built, so:
An optional argument can be added to /_, accepting an odor(or filter) with which to filter the path names.
Alternately, "filtered /_" can be a separate horn altogether, but leaving it specialized to @da seems a bit weird.

CC @cgyarvin, sorry this is less coherent than it could be

:talk on a moon

Upon booting a moon it looks like :talk gets unlinked:

sync succeeded from %kids on ~talsur-todres to %base
[unlinked from [p=~talsur-todres q=%talk]]
/~talsur-todres/home/0/app/talk:<[2.044 3].[2.052 40]>
/~talsur-todres/home/0/app/talk:<[2.045 3].[2.052 40]>
/~talsur-todres/home/0/app/talk:<[2.047 3].[2.052 40]>
/~talsur-todres/home/0/app/talk:<[2.048 5].[2.050 42]>
mack
; ~talsur-todres is ok

[Edited because the last part was just a matter of ~doznec/urbit-meta vs /urbit-meta since ~talsur-todres is my parent here]

|rm crashes on incorrect path

So if I try to remove a node that doesn't exist with |rm /=home=/some/broken/path I get:

removed
exit
/~zod/home/~2016.3.3..03.03.07..1601/arvo/hoon:<[10.967 15].[10.998 57]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/hoon:<[10.968 15].[10.998 57]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/hoon:<[10.969 15].[10.998 57]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/hoon:<[10.971 15].[10.998 57]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/hoon:<[10.973 15].[10.998 57]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/hoon:<[10.973 29].[10.973 44]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/hoon:<[11.038 3].[11.043 13]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/hoon:<[11.040 3].[11.043 13]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/hoon:<[11.041 3].[11.043 13]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/hoon:<[11.042 5].[11.042 47]>
[%swim-take-vane %c %made ~]
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.789 3].[2.955 5]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.790 3].[2.955 5]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.808 3].[2.955 5]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.822 3].[2.955 5]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.827 5].[2.913 7]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.828 5].[2.913 7]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.830 7].[2.837 17]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.831 7].[2.837 17]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.832 7].[2.837 17]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.833 7].[2.837 17]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.834 7].[2.837 17]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.835 9].[2.836 46]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.836 9].[2.836 46]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[2.836 14].[2.836 46]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[709 5].[725 32]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[710 5].[725 32]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[712 5].[725 32]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[714 5].[725 32]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[714 9].[719 13]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[715 9].[719 13]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[718 11].[718 27]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[678 5].[705 51]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[679 5].[705 51]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[701 5].[705 51]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[701 9].[701 33]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[701 13].[701 33]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.442 7].[1.464 9]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.443 7].[1.464 9]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.445 12].[1.459 25]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.446 16].[1.449 55]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.483 7].[1.488 12]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.486 7].[1.488 12]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.486 11].[1.486 55]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.486 15].[1.486 55]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.486 27].[1.486 46]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.351 7].[1.401 9]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.352 7].[1.401 9]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.358 7].[1.401 9]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.367 7].[1.401 9]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.367 16].[1.401 9]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.368 7].[1.401 9]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.370 7].[1.401 9]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.371 7].[1.401 9]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.382 9].[1.383 28]>
/~zod/home/~2016.3.3..03.03.07..1601/arvo/clay:<[1.382 57].[1.382 59]>

One would hope for an error message, right?

[unmerged] :twit prints a link to any successfully posted message

This is useful for demo purposes but should be replaced with getting the post back via long-poll. Or for that matter pre-loading it into the user station, but still not as a %app message.

~$(foo ...) should be ~$(%foo ...)

for consistency with other hint syntaxes etc.

Syntax proposal: a~foo for |*(_[b=+<:foo c=+<:a:foo] (~(a foo b) c))

My crusade against parens continues: (gas~in a b) is much cleaner than (~(gas in a) b), not speaking of :(uni~by a b c d) or (roll (list (set))foo int~in)

The expansion could be better, but the purpose is hopefully clear.

++boil should reject [foo bar] old-syntax tiles

perform other sanity checks in %herb interpretation, an atom or cell is not a valid herb.

Api connectors match domains exactly

www.googleapis.com and pubsub.googleapis.com expect the same authentication session, but eyre currently keys sessions on the full domain.

Permissions in clay

Part of the reason sec/ drivers use an opaque atom type for keys is the encryption those go through to be stored on disk.

Also, in general filesystems can contain private data.

<-:1> prints a very verbose and confusing type error

%fire-core -fire-span.{<1.abr {#t *} ...> {huge subject type}}

While trying to pretty-print void is certainly an error, and even one I am somewhat thankful to the typesystem for catching, "fire-core" is not the most helpful of messages to print there.

META: migrate urbit/urbit issues

Anything that isn't directly a vere issue should be moved here. @philipcmonk, do you remember how e.g. urbit/urbit#139 was migrated?

Web dojo does not allow paste.

Likely this is due to whatever input mechanism you are using. However as new people arrive they are going to want to paste examples from tutorials and docs into the /dojo and will be confused as to why it doesn't work.

This is either a bug or an enhancement request depending on how you want to categorize it :-)

Potential problem in the security driver autoreload system

After starting a fakezod on a DO droplet, and making a shim com/googleapis/pubsub to deal with #4, @ault011 is still getting 401s. Track down, eliminate.

Change "backspace at start of line" to "backspace on empty line"

As the trigger for "clear", which exits dialogs, multiline hoon, etc.

Sole scroller always right-aligning is confusing

Currently, if you type more than termwidth characters, the left side of your input scrolls off the side of your prompt; and if you go back any, anything to the right of the cursor scrolls back off the right side. Would it make more sense for the current visible slice to be "sticky", with only motion to the left or right edges moving it? I know I find it confusing when I see a typo, scroll back to it, and can no longer see the five words I've entered since.

Clay off by one (?)

This is a strange one, and probably difficult to reproduce. The short of it is that I got a weird sync that clipped the last character off every file in clay. Email thread:

https://groups.google.com/d/msg/urbit-dev/BY8ePTgkulw/5EW0yB64IwAJ

~doznec flips out spamming %lost-gram-thou on every reset

Just noticed this. Tons of lines of this:

[%lost-gram-thou [p=~doznec q=~talsur-todres] 0v3.8hreb.nkvif.e5fq3.3ofo0.nsp9h]
[%lost-gram-thou [p=~doznec q=~talsur-todres] 0v3.8hreb.nkvif.e5fq3.3ofo0.nsp9h]
[%lost-gram-thou [p=~doznec q=~talsur-todres] 0v3.8hreb.nkvif.e5fq3.3ofo0.nsp9h]
[%lost-gram-thou [p=~doznec q=~talsur-todres] 0v3.8hreb.nkvif.e5fq3.3ofo0.nsp9h]
[%lost-gram-thou [p=~doznec q=~talsur-todres] 0v3.8hreb.nkvif.e5fq3.3ofo0.nsp9h]

Mark translation from httr to user-type through json should work

Expand the single-layer grab to better handle response translation.

Reintroduce ren/red-quri.hoon

~talsur-todres= how do i write a redirect?
--------[4.550]
~talsur-todres= (that's for fyr too)
...
          ~fyr@ could have sworn there was a ren/red-quri checked in
          ~fyr= maybe it got "cleaned" along with the docs?

It used to exist, probably got deleted because it was used only to point /doc to /docs, should exist again to demonstrate how to set up redirects.

no favicon

Our beloved hardcoded-into-eyre favicon has gone missing...

mug hoon doesn't snip to 31 bits for pairs

Try running (mug [0 151]) using the hoon code, not the jet, you should get a value with bit 32 set.

I think this line should be

?. =(0 d) d

instead.

Gall peek failures should indicate cause of failure somehow

For clay, the semantics of a crashed .^ are fairly straightforward: %y never crashes, %x crashes if a file does not exist at the desk at this time. For gall, either can crash, leaving just the path in the stack trace, regardless of whether:

The application is not started
The application detected a formatting error in your path, and attempted to report it via ~|
The request was not made at the current date(currently unchecked, but necessary for referential transparency)

=/ and =; don't exist

except in ++open and by comment in ++expo. Are there supposed to be ir/regular forms for these?

[%swim-lost %e %went]

Eyre should not get any wents. Eyre uses the e2e ames path.

Partially resolved by #46: since eyre ignores acknowledgements either way, ignoring the wrong type shouldn't cause huge problems.