urbit/pkg/arvo/app/goad.hoon

/+  default-agent, verb
%+  verb  |
^-  agent:gall
=>
  |%
  ++  goad
    |=  force=?
    :~  [%pass /gall %arvo %g %goad force ~]
    ==
  --
|_  =bowl:gall
+*  this  .
    def  ~(. (default-agent this %|) bowl)
::
++  on-poke
  |=  [=mark =vase]
  ?:  ?=([%noun * %go] +<)
    [(goad |) this]
  ?:  ?=([%noun * %force] +<)
    [(goad &) this]
  (on-poke:def mark vase)
::
++  on-arvo
  |=  [wir=wire sin=sign-arvo]
  ?+  wir  (on-arvo:def wir sin)
    [%clay ~]  `this
    [%behn ~]  `this  ::  backcompat
  ==
::
++  on-agent  on-agent:def
++  on-fail   on-fail:def
++  on-init   on-init:def
++  on-leave  on-leave:def
++  on-load   on-load:def
++  on-peek   on-peek:def
++  on-save   on-save:def
++  on-watch  on-watch:def
--
goad: recompile apps after changes to /sys OTAs commonly end up in an inconsistent state if apps depend on changes to /sys. For example, the %sift changes break on OTA because %spider needs to be reloaded so that it's aware of the new thread type. This adds a %goad app, which reloads all apps after every change to /sys. Getting this to start OTA is nontrivial, but this pattern should work for apps in the future. The changes to clock shouldn't generally be necessary; they are only necessary here because we can't rely on hood to start goad, since hood fails to compile if it's run before zuse is reloaded. Once goad is active, this will cease to be a problem. 2019-12-14 03:32:13 +03:00			`/+ default-agent, verb`
			`%+ verb \|`
			`^- agent:gall`
			`=>`
			`\|%`
			`++ goad`
goad: make startup resilient to errors By not running the risky %goad card in on-init. Also includes some qol fixes. 2019-12-14 05:40:12 +03:00			`\|= force=?`
			`:~ [%pass /gall %arvo %g %goad force ~]`
goad: recompile apps after changes to /sys OTAs commonly end up in an inconsistent state if apps depend on changes to /sys. For example, the %sift changes break on OTA because %spider needs to be reloaded so that it's aware of the new thread type. This adds a %goad app, which reloads all apps after every change to /sys. Getting this to start OTA is nontrivial, but this pattern should work for apps in the future. The changes to clock shouldn't generally be necessary; they are only necessary here because we can't rely on hood to start goad, since hood fails to compile if it's run before zuse is reloaded. Once goad is active, this will cease to be a problem. 2019-12-14 03:32:13 +03:00			`==`
			`--`
			`\|_ =bowl:gall`
			`+* this .`
			`def ~(. (default-agent this %\|) bowl)`
gall: WIP load-lost 2020-06-10 11:16:25 +03:00			`::`
goad: make startup resilient to errors By not running the risky %goad card in on-init. Also includes some qol fixes. 2019-12-14 05:40:12 +03:00			`++ on-poke`
			`\|= [=mark =vase]`
			`?: ?=([%noun * %go] +<)`
			`[(goad \|) this]`
			`?: ?=([%noun * %force] +<)`
			`[(goad &) this]`
			`(on-poke:def mark vase)`
			`::`
gall: WIP load-lost 2020-06-10 11:16:25 +03:00			`++ on-arvo`
			`\|= [wir=wire sin=sign-arvo]`
			`?+ wir (on-arvo:def wir sin)`
			[%clay ~] `this
goad: don't crash on pre-OTA sign 2020-06-29 09:43:52 +03:00			[%behn ~] `this :: backcompat
gall: WIP load-lost 2020-06-10 11:16:25 +03:00			`==`
			`::`
goad: recompile apps after changes to /sys OTAs commonly end up in an inconsistent state if apps depend on changes to /sys. For example, the %sift changes break on OTA because %spider needs to be reloaded so that it's aware of the new thread type. This adds a %goad app, which reloads all apps after every change to /sys. Getting this to start OTA is nontrivial, but this pattern should work for apps in the future. The changes to clock shouldn't generally be necessary; they are only necessary here because we can't rely on hood to start goad, since hood fails to compile if it's run before zuse is reloaded. Once goad is active, this will cease to be a problem. 2019-12-14 03:32:13 +03:00			`++ on-agent on-agent:def`
			`++ on-fail on-fail:def`
gall: WIP load-lost 2020-06-10 11:16:25 +03:00			`++ on-init on-init:def`
			`++ on-leave on-leave:def`
			`++ on-load on-load:def`
			`++ on-peek on-peek:def`
			`++ on-save on-save:def`
			`++ on-watch on-watch:def`
goad: recompile apps after changes to /sys OTAs commonly end up in an inconsistent state if apps depend on changes to /sys. For example, the %sift changes break on OTA because %spider needs to be reloaded so that it's aware of the new thread type. This adds a %goad app, which reloads all apps after every change to /sys. Getting this to start OTA is nontrivial, but this pattern should work for apps in the future. The changes to clock shouldn't generally be necessary; they are only necessary here because we can't rely on hood to start goad, since hood fails to compile if it's run before zuse is reloaded. Once goad is active, this will cease to be a problem. 2019-12-14 03:32:13 +03:00			`--`