Register R368: a moved path is no shrink, and a shrink at the new path still is (hq issue 368) #77

2026-10-10T16:09:27Z

mesh-admin commented

2026-10-10 16:09:27 +00:00

Registers the replay of hq issue 368 (the data-shrank watch compared two different directories after a path change), fixed by mesh-controller#204 (merge 798738c).

The replay is the controller's TestAMovedPathIsNoShrinkAndAShrinkThereStillIs in cmd/mesh-controller/data_test.go, written only with what the controller had before the fix, laid over the commit before it.

Proved locally with go run ./cmd/prove --repos <clones> R368 against postgres 17:

R368 (issue 368): PROVED — before its fix fails, on its fix passes
  before: data_test.go:201: a moved path raised a shrink: ... shrank to 490 B from 90.3 MB within 7 days ...

replays/merge-check.sh passes (TestEveryReplayIsWhole).

Registers the replay of hq issue 368 (the data-shrank watch compared two different directories after a path change), fixed by mesh-controller#204 (merge 798738c). The replay is the controller's `TestAMovedPathIsNoShrinkAndAShrinkThereStillIs` in `cmd/mesh-controller/data_test.go`, written only with what the controller had before the fix, laid over the commit before it. Proved locally with `go run ./cmd/prove --repos <clones> R368` against postgres 17: R368 (issue 368): PROVED — before its fix fails, on its fix passes before: data_test.go:201: a moved path raised a shrink: ... shrank to 490 B from 90.3 MB within 7 days ... `replays/merge-check.sh` passes (TestEveryReplayIsWhole).

mesh-admin added 1 commit 2026-10-10 16:09:27 +00:00

Register R368: a moved path is no shrink, and a shrink at the new path still is (hq issue 368)

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check fail: merge-check.sh (typescript), replays/merge-check.sh (go) passed; its asks/merge-check.sh failed: --- FAIL: TestTheOperatorsAnswerEndT…

Details

mesh/delivery superseded: a newer head of the same pull request

Details

95736b0eab

mesh-admin commented

2026-10-10 16:09:31 +00:00

Delivery novox/mesh-lab@b3d6d65db1f8 — delivered since 2026-10-10T16:33:06Z

Delivery plan — builds nothing: the change touches no module of the mesh's graph

Transitions

2026-10-10 16:28 (new) → proposed (announced): novox/mesh-lab#77's head announced
2026-10-10 16:31 proposed → checked (checked): the verdict names this commit
2026-10-10 16:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-10 16:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-10 16:33 published → delivered (done): nothing for a walk to move

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-lab@b3d6d65db1f8` — **delivered** since 2026-10-10T16:33:06Z **Delivery plan** — builds nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-10 16:28 (new) → proposed (announced): novox/mesh-lab#77's head announced - 2026-10-10 16:31 proposed → checked (checked): the verdict names this commit - 2026-10-10 16:31 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-10 16:33 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-10 16:33 published → delivered (done): nothing for a walk to move The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

mesh-admin commented

2026-10-10 16:09:56 +00:00

Independent review (a separate reviewer agent), approved at head 95736b0: the entry follows R335/R336; Fix 798738c is the merge of mesh-controller#204 (first parent 4d30b5d); the test exists at that commit in cmd/mesh-controller/data_test.go; role names and glossary words only. Pointing at the shared data_test.go rather than a replayNNN_test.go is accepted, as R362 does; the replay was proved on both sides of the fix.

Independent review (a separate reviewer agent), approved at head 95736b0: the entry follows R335/R336; Fix 798738c is the merge of mesh-controller#204 (first parent 4d30b5d); the test exists at that commit in cmd/mesh-controller/data_test.go; role names and glossary words only. Pointing at the shared data_test.go rather than a replayNNN_test.go is accepted, as R362 does; the replay was proved on both sides of the fix.

mesh-admin commented

2026-10-10 16:13:18 +00:00

Merge check at 95736b0e

mesh/merge-gate: PASS — the change touches no module of the mesh's graph
mesh/repo-check: FAIL — merge-check.sh (typescript), replays/merge-check.sh (go) passed; its asks/merge-check.sh failed: --- FAIL: TestTheOperatorsAnswerEndToEnd (158.27s)

Run by the build seat on shanks as build-1791648568859603064 (builds --log build-1791648568859603064).

  type: 'test'
  ...
# Subtest: two addresses of one family on one attachment is refused
ok 145 - two addresses of one family on one attachment is refused
  ---
  duration_ms: 0.684638
  type: 'test'
  ...
# Subtest: place naming a machine that does not exist is refused
ok 146 - place naming a machine that does not exist is refused
  ---
  duration_ms: 0.769269
  type: 'test'
  ...
# Subtest: every problem is reported, not just the first
ok 147 - every problem is reported, not just the first
  ---
  duration_ms: 0.80983
  type: 'test'
  ...
# Subtest: a detached machine is valid
ok 148 - a detached machine is valid
  ---
  duration_ms: 0.728979
  type: 'test'
  ...
# Subtest: a multi-homed machine is valid
ok 149 - a multi-homed machine is valid
  ---
  duration_ms: 0.82892
  type: 'test'
  ...
# Subtest: an isolated private segment with no gateway is valid — a site with no internet
ok 150 - an isolated private segment with no gateway is valid — a site with no internet
  ---
  duration_ms: 0.485816
  type: 'test'
  ...
# Subtest: two gateways sharing an address are one gateway, not two
ok 151 - two gateways sharing an address are one gateway, not two
  ---
  duration_ms: 2.108335
  type: 'test'
  ...
# Subtest: one box cannot behave two ways
ok 152 - one box cannot behave two ways
  ---
  duration_ms: 0.968972
  type: 'test'
  ...
# Subtest: a detached machine cannot declare egress
ok 153 - a detached machine cannot declare egress
  ---
  duration_ms: 0.417855
  type: 'test'
  ...
# Subtest: a third-party image in images: is refused, because nothing loads it
ok 154 - a third-party image in images: is refused, because nothing loads it
  ---
  duration_ms: 1.492608
  type: 'test'
  ...
# Subtest: one of ours in images: is accepted
ok 155 - one of ours in images: is accepted
  ---
  duration_ms: 0.529227
  type: 'test'
  ...
# Subtest: images: is named by tag — an image ID is not knowable until the image is built
ok 156 - images: is named by tag — an image ID is not knowable until the image is built
  ---
  duration_ms: 0.511806
  type: 'test'
  ...
# Subtest: a machine cannot be handed an image the scenario does not have
ok 157 - a machine cannot be handed an image the scenario does not have
  ---
  duration_ms: 0.578017
  type: 'test'
  ...
# Subtest: a segment may not be named 'uplink' — the lab claims that name for egress
ok 158 - a segment may not be named 'uplink' — the lab claims that name for egress
  ---
  duration_ms: 0.428645
  type: 'test'
  ...
# Subtest: a warm mesh built from code that has moved is refused
ok 159 - a warm mesh built from code that has moved is refused
  ---
  duration_ms: 1.244705
  type: 'test'
  ...
# Subtest: a warm mesh built from the same code is used
ok 160 - a warm mesh built from the same code is used
  ---
  duration_ms: 0.157742
  type: 'test'
  ...
# Subtest: every reason to raise instead says which reason it was
ok 161 - every reason to raise instead says which reason it was
  ---
  duration_ms: 0.269893
  type: 'test'
  ...
# Subtest: a repository that was not recorded when it was warmed is refused
ok 162 - a repository that was not recorded when it was warmed is refused
  ---
  duration_ms: 0.161392
  type: 'test'
  ...
# Subtest: a repository this run cannot locate is refused, not passed over
ok 163 - a repository this run cannot locate is refused, not passed over
  ---
  duration_ms: 0.247303
  type: 'test'
  ...
1..163
# tests 163
# suites 0
# pass 161
# fail 0
# cancelled 0
# skipped 2
# todo 0
# duration_ms 635.689141
replays/ and asks/ (Go) are checked by their merge-check.sh, which the build seat runs in the Go toolchain
NOT RUN HERE: the integration suite and the replays — they need a lab and the container runtime
--- its replays/merge-check.sh (go toolchain)
ok  	github.com/novox/mesh-lab/replays	0.019s
NOT RUN HERE: the replays themselves — they raise containers, and this container holds no container runtime
--- its asks/merge-check.sh (go toolchain)
--- FAIL: TestTheOperatorsAnswerEndToEnd (158.27s)
    --- PASS: TestTheOperatorsAnswerEndToEnd/the_operator_links_their_account_with_the_code_shown_on_the_desk (0.20s)
    --- PASS: TestTheOperatorsAnswerEndToEnd/an_approval_in_the_hour_after_linking_is_refused_and_nothing_is_done (61.90s)
    --- PASS: TestTheOperatorsAnswerEndToEnd/the_hour_after_the_link_passes (0.00s)
    --- PASS: TestTheOperatorsAnswerEndToEnd/approve_does_exactly_the_one_thing,_once,_and_says_who_approved (0.10s)
    --- FAIL: TestTheOperatorsAnswerEndToEnd/a_replayed_tap_and_a_redelivered_warrant_do_nothing_more (90.10s)
FAIL
FAIL	github.com/novox/mesh-lab/asks	158.271s
FAIL
    faketelegram_test.go:84: phone: getUpdates from 2 hands 1 update(s)
    faketelegram_test.go:108: phone: sendMessage to 42 (#4): "Linked. You can answer acknowledgements now, and approve from 17:10." []
    faketelegram_test.go:108: phone: sendMessage to 42 (#5): "A Telegram account is now linked as you …" []
=== RUN   TestTheOperatorsAnswerEndToEnd/an_approval_in_the_hour_after_linking_is_refused_and_nothing_is_done
=== NAME  TestTheOperatorsAnswerEndToEnd
    faketelegram_test.go:108: phone: sendMessage to 42 (#6): "Flip the lab's switch? …" [[Approve a73f6f666afcca48fbd4509b4c63980f] [Decline a37d260d090b5e04a48475a455dd4d70]]
    faketelegram_test.go:84: phone: getUpdates from 3 hands 1 update(s)
    faketelegram_test.go:108: phone: sendMessage to 42 (#8): "That answer was not taken …" []
=== RUN   TestTheOperatorsAnswerEndToEnd/the_hour_after_the_link_passes
=== RUN   TestTheOperatorsAnswerEndToEnd/approve_does_exactly_the_one_thing,_once,_and_says_who_approved
=== NAME  TestTheOperatorsAnswerEndToEnd
    faketelegram_test.go:84: phone: getUpdates from 4 hands 1 update(s)
    faketelegram_test.go:108: phone: editMessageText to 42 (#6): "You chose Approve at 16:11 on Telegram · Flip the lab's switch? …" []
=== NAME  TestTheOperatorsAnswerEndToEnd/approve_does_exactly_the_one_thing,_once,_and_says_who_approved
    proof_test.go:177: the record reads: the operator, via telegram (user id verified), chose Approve
=== RUN   TestTheOperatorsAnswerEndToEnd/a_replayed_tap_and_a_redelivered_warrant_do_nothing_more
=== NAME  TestTheOperatorsAnswerEndToEnd
    faketelegram_test.go:84: phone: getUpdates from 5 hands 1 update(s)
    proof_test.go:184: the phone never showed the refusal of a replayed tap (chat 42) within 1m30s; it showed:
          16:10:43.044 to 42 #2 edited=false "Send the code shown on your desk …" []
          16:10:43.147 to 42 #4 edited=false "Linked. You can answer acknowledgements now, and approve from 17:10." []
          16:10:43.147 to 42 #5 edited=false "A Telegram account is now linked as you …" []
          16:11:42.956 to 42 #6 edited=false "Flip the lab's switch? …" [[Approve a73f6f666afcca48fbd4509b4c63980f] [Decline a37d260d090b5e04a48475a455dd4d70]]
          16:11:43.044 to 42 #8 edited=false "That answer was not taken …" []
          16:11:45.156 to 42 #6 edited=true "You chose Approve at 16:11 on Telegram · Flip the lab's switch? …" []
=== NAME  TestTheOperatorsAnswerEndToEnd/a_replayed_tap_and_a_redelivered_warrant_do_nothing_more
    testing.go:1913: test executed panic(nil) or runtime.Goexit: subtest may have called FailNow on a parent test
=== NAME  TestTheOperatorsAnswerEndToEnd
    harness_test.go:311: --- what the telegram runtime said:
        [mesh-tools] serving 1 tool(s) for 1 module(s): telegram.telegram_status
        [mesh-tools] telegram takes its work from SEAT_CHANNEL_TELEGRAM_worker
        [telegram] [telegram] taking the router's messages for this kind
    harness_test.go:311: --- what the messenger runtime said:
        [mesh-tools] serving 6 tool(s) for 1 module(s): messenger.messenger_status, messenger.messenger_identities, messenger.messenger_unlink, messenger.messenger_recent, messenger.messenger_test, messenger.messenger_check
        [mesh-tools] serving operator-channel's open on mesh.seat.operator-channel.tool.open, admitted where messenger holds the seat
        [mesh-tools] serving operator-channel's history on mesh.seat.operator-channel.tool.history, admitted where messenger holds the seat
        [mesh-tools] serving operator-channel's notify on mesh.seat.operator-channel.tool.notify, admitted where messenger holds the seat
        [mesh-tools] serving operator-channel's asks on mesh.seat.operator-channel.tool.asks, admitted where messenger holds the seat
        [messenger] [messenger] away cannot send: no channel reaching the operator away from the machines is held: a module claims a kind of the channel bench that promises reaches-away (novox/hq ADR 0259)
        [messenger] [messenger] desk cannot send: no channel at the operator's machines is held
        [mesh-tools] messenger's events arrive on its consumer anchor_messenger
        [mesh-tools] messenger answers the proofs on mesh.seat.intake.proof.code.*
        [messenger] [messenger] listening for the controller's condition events
        [messenger] [messenger] answering the codes the channels are sent
        [messenger] [messenger] listening for what the channels say
        [mesh-tools] messenger takes its work from SEAT_OPERATOR_CHANNEL_worker
        [messenger] [messenger] taking the asks submitted to operator-channel
        [messenger] [messenger] a link was asked on telegram by "Account 42" (42); its code is shown on desktop
        [messenger] [messenger] lab-asker asks "Flip the lab's switch?" (a1), shown on ask.lab-asker.a1
        [messenger] [messenger] an answer on telegram from 42 was refused: this account was linked at 16:10 and can answer this question from 17:10
        [messenger] [messenger] the operator, via telegram (user id verified), chose Approve: a warrant for lab-asker's ask a1
--- FAIL: TestTheOperatorsAnswerEndToEnd (158.27s)
    --- PASS: TestTheOperatorsAnswerEndToEnd/the_operator_links_their_account_with_the_code_shown_on_the_desk (0.20s)
    --- PASS: TestTheOperatorsAnswerEndToEnd/an_approval_in_the_hour_after_linking_is_refused_and_nothing_is_done (61.90s)
    --- PASS: TestTheOperatorsAnswerEndToEnd/the_hour_after_the_link_passes (0.00s)
    --- PASS: TestTheOperatorsAnswerEndToEnd/approve_does_exactly_the_one_thing,_once,_and_says_who_approved (0.10s)
    --- FAIL: TestTheOperatorsAnswerEndToEnd/a_replayed_tap_and_a_redelivered_warrant_do_nothing_more (90.10s)
FAIL
FAIL	github.com/novox/mesh-lab/asks	158.271s
FAIL

**Merge check** at `95736b0e` - `mesh/merge-gate`: **PASS** — the change touches no module of the mesh's graph - `mesh/repo-check`: **FAIL** — merge-check.sh (typescript), replays/merge-check.sh (go) passed; its asks/merge-check.sh failed: --- FAIL: TestTheOperatorsAnswerEndToEnd (158.27s) Run by the build seat on shanks as `build-1791648568859603064` (`builds --log build-1791648568859603064`). ``` type: 'test' ... # Subtest: two addresses of one family on one attachment is refused ok 145 - two addresses of one family on one attachment is refused --- duration_ms: 0.684638 type: 'test' ... # Subtest: place naming a machine that does not exist is refused ok 146 - place naming a machine that does not exist is refused --- duration_ms: 0.769269 type: 'test' ... # Subtest: every problem is reported, not just the first ok 147 - every problem is reported, not just the first --- duration_ms: 0.80983 type: 'test' ... # Subtest: a detached machine is valid ok 148 - a detached machine is valid --- duration_ms: 0.728979 type: 'test' ... # Subtest: a multi-homed machine is valid ok 149 - a multi-homed machine is valid --- duration_ms: 0.82892 type: 'test' ... # Subtest: an isolated private segment with no gateway is valid — a site with no internet ok 150 - an isolated private segment with no gateway is valid — a site with no internet --- duration_ms: 0.485816 type: 'test' ... # Subtest: two gateways sharing an address are one gateway, not two ok 151 - two gateways sharing an address are one gateway, not two --- duration_ms: 2.108335 type: 'test' ... # Subtest: one box cannot behave two ways ok 152 - one box cannot behave two ways --- duration_ms: 0.968972 type: 'test' ... # Subtest: a detached machine cannot declare egress ok 153 - a detached machine cannot declare egress --- duration_ms: 0.417855 type: 'test' ... # Subtest: a third-party image in images: is refused, because nothing loads it ok 154 - a third-party image in images: is refused, because nothing loads it --- duration_ms: 1.492608 type: 'test' ... # Subtest: one of ours in images: is accepted ok 155 - one of ours in images: is accepted --- duration_ms: 0.529227 type: 'test' ... # Subtest: images: is named by tag — an image ID is not knowable until the image is built ok 156 - images: is named by tag — an image ID is not knowable until the image is built --- duration_ms: 0.511806 type: 'test' ... # Subtest: a machine cannot be handed an image the scenario does not have ok 157 - a machine cannot be handed an image the scenario does not have --- duration_ms: 0.578017 type: 'test' ... # Subtest: a segment may not be named 'uplink' — the lab claims that name for egress ok 158 - a segment may not be named 'uplink' — the lab claims that name for egress --- duration_ms: 0.428645 type: 'test' ... # Subtest: a warm mesh built from code that has moved is refused ok 159 - a warm mesh built from code that has moved is refused --- duration_ms: 1.244705 type: 'test' ... # Subtest: a warm mesh built from the same code is used ok 160 - a warm mesh built from the same code is used --- duration_ms: 0.157742 type: 'test' ... # Subtest: every reason to raise instead says which reason it was ok 161 - every reason to raise instead says which reason it was --- duration_ms: 0.269893 type: 'test' ... # Subtest: a repository that was not recorded when it was warmed is refused ok 162 - a repository that was not recorded when it was warmed is refused --- duration_ms: 0.161392 type: 'test' ... # Subtest: a repository this run cannot locate is refused, not passed over ok 163 - a repository this run cannot locate is refused, not passed over --- duration_ms: 0.247303 type: 'test' ... 1..163 # tests 163 # suites 0 # pass 161 # fail 0 # cancelled 0 # skipped 2 # todo 0 # duration_ms 635.689141 replays/ and asks/ (Go) are checked by their merge-check.sh, which the build seat runs in the Go toolchain NOT RUN HERE: the integration suite and the replays — they need a lab and the container runtime --- its replays/merge-check.sh (go toolchain) ok github.com/novox/mesh-lab/replays 0.019s NOT RUN HERE: the replays themselves — they raise containers, and this container holds no container runtime --- its asks/merge-check.sh (go toolchain) --- FAIL: TestTheOperatorsAnswerEndToEnd (158.27s) --- PASS: TestTheOperatorsAnswerEndToEnd/the_operator_links_their_account_with_the_code_shown_on_the_desk (0.20s) --- PASS: TestTheOperatorsAnswerEndToEnd/an_approval_in_the_hour_after_linking_is_refused_and_nothing_is_done (61.90s) --- PASS: TestTheOperatorsAnswerEndToEnd/the_hour_after_the_link_passes (0.00s) --- PASS: TestTheOperatorsAnswerEndToEnd/approve_does_exactly_the_one_thing,_once,_and_says_who_approved (0.10s) --- FAIL: TestTheOperatorsAnswerEndToEnd/a_replayed_tap_and_a_redelivered_warrant_do_nothing_more (90.10s) FAIL FAIL github.com/novox/mesh-lab/asks 158.271s FAIL faketelegram_test.go:84: phone: getUpdates from 2 hands 1 update(s) faketelegram_test.go:108: phone: sendMessage to 42 (#4): "Linked. You can answer acknowledgements now, and approve from 17:10." [] faketelegram_test.go:108: phone: sendMessage to 42 (#5): "A Telegram account is now linked as you …" [] === RUN TestTheOperatorsAnswerEndToEnd/an_approval_in_the_hour_after_linking_is_refused_and_nothing_is_done === NAME TestTheOperatorsAnswerEndToEnd faketelegram_test.go:108: phone: sendMessage to 42 (#6): "Flip the lab's switch? …" [[Approve a73f6f666afcca48fbd4509b4c63980f] [Decline a37d260d090b5e04a48475a455dd4d70]] faketelegram_test.go:84: phone: getUpdates from 3 hands 1 update(s) faketelegram_test.go:108: phone: sendMessage to 42 (#8): "That answer was not taken …" [] === RUN TestTheOperatorsAnswerEndToEnd/the_hour_after_the_link_passes === RUN TestTheOperatorsAnswerEndToEnd/approve_does_exactly_the_one_thing,_once,_and_says_who_approved === NAME TestTheOperatorsAnswerEndToEnd faketelegram_test.go:84: phone: getUpdates from 4 hands 1 update(s) faketelegram_test.go:108: phone: editMessageText to 42 (#6): "You chose Approve at 16:11 on Telegram · Flip the lab's switch? …" [] === NAME TestTheOperatorsAnswerEndToEnd/approve_does_exactly_the_one_thing,_once,_and_says_who_approved proof_test.go:177: the record reads: the operator, via telegram (user id verified), chose Approve === RUN TestTheOperatorsAnswerEndToEnd/a_replayed_tap_and_a_redelivered_warrant_do_nothing_more === NAME TestTheOperatorsAnswerEndToEnd faketelegram_test.go:84: phone: getUpdates from 5 hands 1 update(s) proof_test.go:184: the phone never showed the refusal of a replayed tap (chat 42) within 1m30s; it showed: 16:10:43.044 to 42 #2 edited=false "Send the code shown on your desk …" [] 16:10:43.147 to 42 #4 edited=false "Linked. You can answer acknowledgements now, and approve from 17:10." [] 16:10:43.147 to 42 #5 edited=false "A Telegram account is now linked as you …" [] 16:11:42.956 to 42 #6 edited=false "Flip the lab's switch? …" [[Approve a73f6f666afcca48fbd4509b4c63980f] [Decline a37d260d090b5e04a48475a455dd4d70]] 16:11:43.044 to 42 #8 edited=false "That answer was not taken …" [] 16:11:45.156 to 42 #6 edited=true "You chose Approve at 16:11 on Telegram · Flip the lab's switch? …" [] === NAME TestTheOperatorsAnswerEndToEnd/a_replayed_tap_and_a_redelivered_warrant_do_nothing_more testing.go:1913: test executed panic(nil) or runtime.Goexit: subtest may have called FailNow on a parent test === NAME TestTheOperatorsAnswerEndToEnd harness_test.go:311: --- what the telegram runtime said: [mesh-tools] serving 1 tool(s) for 1 module(s): telegram.telegram_status [mesh-tools] telegram takes its work from SEAT_CHANNEL_TELEGRAM_worker [telegram] [telegram] taking the router's messages for this kind harness_test.go:311: --- what the messenger runtime said: [mesh-tools] serving 6 tool(s) for 1 module(s): messenger.messenger_status, messenger.messenger_identities, messenger.messenger_unlink, messenger.messenger_recent, messenger.messenger_test, messenger.messenger_check [mesh-tools] serving operator-channel's open on mesh.seat.operator-channel.tool.open, admitted where messenger holds the seat [mesh-tools] serving operator-channel's history on mesh.seat.operator-channel.tool.history, admitted where messenger holds the seat [mesh-tools] serving operator-channel's notify on mesh.seat.operator-channel.tool.notify, admitted where messenger holds the seat [mesh-tools] serving operator-channel's asks on mesh.seat.operator-channel.tool.asks, admitted where messenger holds the seat [messenger] [messenger] away cannot send: no channel reaching the operator away from the machines is held: a module claims a kind of the channel bench that promises reaches-away (novox/hq ADR 0259) [messenger] [messenger] desk cannot send: no channel at the operator's machines is held [mesh-tools] messenger's events arrive on its consumer anchor_messenger [mesh-tools] messenger answers the proofs on mesh.seat.intake.proof.code.* [messenger] [messenger] listening for the controller's condition events [messenger] [messenger] answering the codes the channels are sent [messenger] [messenger] listening for what the channels say [mesh-tools] messenger takes its work from SEAT_OPERATOR_CHANNEL_worker [messenger] [messenger] taking the asks submitted to operator-channel [messenger] [messenger] a link was asked on telegram by "Account 42" (42); its code is shown on desktop [messenger] [messenger] lab-asker asks "Flip the lab's switch?" (a1), shown on ask.lab-asker.a1 [messenger] [messenger] an answer on telegram from 42 was refused: this account was linked at 16:10 and can answer this question from 17:10 [messenger] [messenger] the operator, via telegram (user id verified), chose Approve: a warrant for lab-asker's ask a1 --- FAIL: TestTheOperatorsAnswerEndToEnd (158.27s) --- PASS: TestTheOperatorsAnswerEndToEnd/the_operator_links_their_account_with_the_code_shown_on_the_desk (0.20s) --- PASS: TestTheOperatorsAnswerEndToEnd/an_approval_in_the_hour_after_linking_is_refused_and_nothing_is_done (61.90s) --- PASS: TestTheOperatorsAnswerEndToEnd/the_hour_after_the_link_passes (0.00s) --- PASS: TestTheOperatorsAnswerEndToEnd/approve_does_exactly_the_one_thing,_once,_and_says_who_approved (0.10s) --- FAIL: TestTheOperatorsAnswerEndToEnd/a_replayed_tap_and_a_redelivered_warrant_do_nothing_more (90.10s) FAIL FAIL github.com/novox/mesh-lab/asks 158.271s FAIL ```

jschoubben added 1 commit 2026-10-10 16:27:52 +00:00

Merge main into replay/368: the asks check fixed for issue 393 (#78 )

mesh/merge-gate pass: the change touches no module of the mesh's graph

Details

mesh/repo-check pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (typescript), replays/merge-check.sh (go), asks/merge-check.sh …

Details

mesh/delivery delivered

Details

b3d6d65db1

mesh-admin commented

2026-10-10 16:27:56 +00:00

Merged main into this branch (head b3d6d65) so its mesh/repo-check runs the asks check as fixed by #78 (issue 393). The pull request's own diff against main is byte-for-byte the one reviewed and approved at 95736b0 (12 lines in replays/register.go); the merge commit brings in nothing else of this change.

Merged main into this branch (head b3d6d65) so its mesh/repo-check runs the asks check as fixed by #78 (issue 393). The pull request's own diff against main is byte-for-byte the one reviewed and approved at 95736b0 (12 lines in replays/register.go); the merge commit brings in nothing else of this change.

mesh-admin merged commit 858b15a1a3 into main

2026-10-10 16:32:48 +00:00

mesh-admin deleted branch replay/368-a-moved-path-is-no-shrink

2026-10-10 16:32:48 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-lab#77