aboutsummaryrefslogtreecommitdiffstats
path: root/packages/meshbay-node/tests/test_index_no_cleartext.py
diff options
context:
space:
mode:
authorChristophe Besson <cbesson@gmail.com>2026-09-14 11:08:12 +0200
committerChristophe Besson <cbesson@gmail.com>2026-09-14 11:08:12 +0200
commita294c1d338ba4c20d66873d593d1c101e69c5a40 (patch)
tree7a2f78348f469a46b7df236230f13387e583639c /packages/meshbay-node/tests/test_index_no_cleartext.py
parentd5b4d728b05f68f713fa09edf47c253b869e0f88 (diff)
downloadmeshbay-a294c1d338ba4c20d66873d593d1c101e69c5a40.tar.gz
feat(node): progress names the root under way and the roots waiting
`IndexProgress` said "scanning, this many bytes of that many" and nothing more. A group's roots are walked one after another, so a second directory added during a large scan showed as the bar jumping back to 0 %. It now also carries the root being walked and its position in the roots table, the kind of walk (scan, rescan, reconcile, watch), file counts, and the roots waiting for the scan lock in order: queued by the initial scan, by a retarget, and by a plug; dropped when a root is removed. `GET /api/index-status` answers for every group at once, including a group still in its initial scan, so a client can show indexing on any page. It names roots: loopback only, like `current_dir`. `index_progress` and the handshake ack gain the same counters, still naming nothing (decision D3): the root is a position in the roots table the member already opened from the sealed index, and the queue is a count. The pusher keeps speaking while a root only waits for the lock. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01T6jPTeocXA1BePekdsgPya
Diffstat (limited to 'packages/meshbay-node/tests/test_index_no_cleartext.py')
-rw-r--r--packages/meshbay-node/tests/test_index_no_cleartext.py8
1 files changed, 7 insertions, 1 deletions
diff --git a/packages/meshbay-node/tests/test_index_no_cleartext.py b/packages/meshbay-node/tests/test_index_no_cleartext.py
index f510884..e5e4555 100644
--- a/packages/meshbay-node/tests/test_index_no_cleartext.py
+++ b/packages/meshbay-node/tests/test_index_no_cleartext.py
@@ -151,9 +151,15 @@ def test_index_progress_stays_clear_and_stays_counters():
dicts = [n for n in ast.walk(tree) if isinstance(n, ast.Dict)]
assert len(dicts) == 1, "more than one message built here — re-read this test"
keys = {k.value for k in dicts[0].keys}
+ # `kind` is one of four fixed words and `root_pos`/`queued` are integers —
+ # the root names themselves stay on the loopback API.
assert keys == {"type", "v", "group_id",
- "scanning", "scanned_bytes", "total_bytes"}, (
+ "scanning", "scanned_bytes", "total_bytes",
+ "files_done", "files_total", "kind", "root_pos", "queued"}, (
f"index_progress now carries {keys} — re-read decision D3 before shipping it")
+ values = {k.value: v for k, v in zip(dicts[0].keys, dicts[0].values)}
+ assert ast.unparse(values["queued"]) == "len(progress.queued)", (
+ "the roots waiting must go out as a count, never as their names")
assert "seal(" not in source
assert "D3" in source, "the reason it is not sealed must stay next to the code"