diff options
Diffstat (limited to 'packages/meshbay-hub/tests/test_upload_controls_hidden.py')
| -rw-r--r-- | packages/meshbay-hub/tests/test_upload_controls_hidden.py | 13 |
1 files changed, 7 insertions, 6 deletions
diff --git a/packages/meshbay-hub/tests/test_upload_controls_hidden.py b/packages/meshbay-hub/tests/test_upload_controls_hidden.py index bdba373..f6f476e 100644 --- a/packages/meshbay-hub/tests/test_upload_controls_hidden.py +++ b/packages/meshbay-hub/tests/test_upload_controls_hidden.py @@ -212,16 +212,17 @@ def test_the_notice_also_answers_the_operators_own_request(): caused it. Every other admin ack can be resolved and dropped, because its caller - already knows what it asked for and updates local state from that. The root - acks carry a whole table only the node can compute — availability, the name - it settled on, the eject a failed plug left in place — so resolving one - without handing it on left the operator who clicked Eject as the only - client that never saw it happen. + already knows what it asked for and updates local state from that. These + are the ones the node *broadcasts*: every other connected client learns the + change from it, and the one that asked is the only one that does not, + because its own request swallowed its copy. Found on the root table, then + again on Chat's directory — where it meant the pane went on showing an + unsaved-looking draft after a save that had worked. """ transport = TRANSPORT.read_text(encoding="utf-8") block = transport[transport.index("msg.type.endsWith('_ack')"):] block = block[:block.index("_uploaders")] - assert "ROOT_ACK_TYPES" in block and "_onRootsChanged" in block, ( + assert "BROADCAST_ACK_TYPES" in block and "_replayBroadcast" in block, ( "the initiating client resolves the ack and learns nothing from it") |