@@ -75,7 +75,7 @@ We note that this is mostly the same as `await-thread:strandio`.
7575;< ~ bind:m %- poke-our
7676 :* %spider
7777 %spider-start
78− !>([`tid.bowl `tid byk.bowl %child !>(~)])
78+ !>([`tid.bowl `tid byk.bowl(q da+now.bowl) %child !>(~)])
7979 ==
8080;< =cage bind:m (take-fact /awaiting/[tid])
8181;< ~ bind:m (take-kick /awaiting/[tid])
@@ -131,7 +131,7 @@ We pre-emptively subscribe for the result. Spider sends the result at `/thread-r
131131;< ~ bind:m %- poke-our
132132 :* %spider
133133 %spider-start
134− !>([`tid.bowl `tid byk.bowl %child !>(~)])
134+ !>([`tid.bowl `tid byk.bowl(q da+now.bowl) %child !>(~)])
135135 ==
136136```
137137
@@ -139,7 +139,9 @@ Spider takes a poke with a mark %spider-start and a vase containing `[parent=(un
139139
140140- `parent` is an optional parent thread. In this case we say the parent is our tid. Specifying a parent means the child will be killed if the parent ends.
141141- `use` is the thread ID for the thread we're creating
142−- `beak` is a `[p=ship q=desk r=case]` triple which specifies the desk and revision containing the thread we want to run. In this case we just use `byk.bowl`.
142+- `beak` is a `[p=ship q=desk r=case]` triple which specifies the desk and
143+ revision containing the thread we want to run. In this case we just use
144+ `byk.bowl`, but with the date of revision `q` changed to `now.bowl`.
143145- `file` is the filename of the thread we want to start
144146- `vase` is the vase it will be given as an argument when it's started
145147
@@ -182,7 +184,7 @@ Finally we test whether the thread produced a `%thread-done` or a `%thread-fail`
182184;< ~ bind:m %- poke-our
183185 :* %spider
184186 %spider-start
185− !>([`tid.bowl byk.bowl `tid %child !>(~)])
187+ !>([`tid.bowl byk.bowl(q da+now.bowl) `tid %child !>(~)])
186188 ==
187189;< ~ bind:m (sleep ~s5)
188190%- (slog leaf+"Stopping child thread..." ~)