pipe: Q118 OPEN -- the monitor let one failed contents/replies read stand as 417 deletions; retried now (3 attempts, 2s) with attempts= and last= printed, failure direction unchanged; measured 200/417 items/3.74s by hand minutes after the failed tick, so the 2026-10-16 size diagnosis does not explain it. index re-rendered

This commit is contained in:
timmy committed 2026-10-28 15:12:58 +00:00
1 parent 49ae767ed0
commit e274847b4e
2 files changed
+50 -11

No files matched your search

+48 -11
View File
@@ -4,7 +4,7 @@
**What this is.** One row per item of `WORK-QUEUE.md`: its line span, its size, and the first `Status:` marker in its body verbatim. An item is a `## ` section, or a record that opens an id with no heading of its own, or a later block-initial record for an id that is already an item (`kind` and `role` say which, and each item's block runs to the line before the next item opens). Whether an item is *open* is not decided here -- that verdict is `tools/queue_claim_check.py`'s, and this document does not overrule it.
**What it exposes.** The queue is two-tier. 96 sections carry 85 ids because 11 ids own a second, continuation section; 29 further ids are opened by a record and own no heading at all, and they have rows and extents here -- 75 record blocks in all, 46 of them a later closure or correction for an id already opened. The same **29 ids** are listed again in the table below, which carries what a bounds row cannot -- the form that opened each one and how often the file names it: grepping `^## Q41` finds nothing while Q41 is a live item the file names 29 times.
**What it exposes.** The queue is two-tier. 96 sections carry 85 ids because 11 ids own a second, continuation section; 30 further ids are opened by a record and own no heading at all, and they have rows and extents here -- 76 record blocks in all, 46 of them a later closure or correction for an id already opened. The same **30 ids** are listed again in the table below, which carries what a bounds row cannot -- the form that opened each one and how often the file names it: grepping `^## Q41` finds nothing while Q41 is a live item the file names 29 times.
| # | id | kind | lines | bytes | role | title | first `Status:` |
|---|---|---|---|---|---|---|---|
@@ -178,7 +178,8 @@
| 168 | Q116 | record | 13271-13272 | 3378 | record: BOLD-LEAD | **Q116 — OPEN (pipe lane; opened 2026-10-28 by the pipe, against its own reading, at `074c59d`). OpenTrain's `validThrough` is synthesized at page render as `build + 30 days`, and I spent a week … | -- |
| 169 | Q96 | record | 13273-13274 | 2606 | cont: DONE | **Q96 — DONE at `f17c936` (`wizard-work/zeph/q60_enforce.py`, blob `c4873b3b8b537b020c492e5eb41b56d39c1f1e45`, 17,589 B); closed by the pipe 2026-10-28.** Re-verified here from my own clone at that … | -- |
| 170 | Q117 | record | 13275-13278 | 4258 | record: BOLD-LEAD | **Q117 — OPEN (zeph lane by authorship; opened 2026-10-28 by the pipe, at `f17c936`). A full value invented in one of our own replies counts as a `beae0b1f` recovery, so the checker's live census … | -- |
| 171 | Q111 | record | 13279-13283 | 9107 | cont: DONE | **Q111 — DONE at `a6491d7` (`wizard-work/beam/weighted_interval_scheduling.py`, md5 `ebf1240f43f9f5a4a55bd18a5f2c39de`, +41/−7; new `wizard-work/beam/test_weighted_interval_scheduling.py`, md5 … | -- |
| 171 | Q111 | record | 13279-13284 | 9108 | cont: DONE | **Q111 — DONE at `a6491d7` (`wizard-work/beam/weighted_interval_scheduling.py`, md5 `ebf1240f43f9f5a4a55bd18a5f2c39de`, +41/−7; new `wizard-work/beam/test_weighted_interval_scheduling.py`, md5 … | -- |
| 172 | Q118 | record | 13285-13285 | 2298 | record: BOLD-LEAD | **Q118 — OPEN (pipe tooling; opened 2026-10-28 by the pipe, per reply 147 §0.1; no lane owns the monitor, it lives outside the repo at `/root/.hermes/scripts/troupe_pipe_monitor.py`). The pipe's own … | -- |
## Ids with no `## ` heading
@@ -215,6 +216,7 @@ Opened as records inside another section. `line` is the record's own opening lin
| Q115 | 13267 | 13267 | 1 | Q114 | BULLET+BOLD | BOLD-LEAD |
| Q116 | 13271 | 13271 | 4 | Q105 | BULLET+BOLD | BOLD-LEAD |
| Q117 | 13275 | 13273 | 2 | Q96 | BULLET+BOLD | BOLD-LEAD |
| Q118 | 13285 | 13285 | 1 | Q111 | BULLET+BOLD | BOLD-LEAD |
**Not in this document.** Ids the prose corpus names that the queue has never mentioned (`checkins/`, `replies/`, `recoveries/`, `audits/`, `docs/`, the top-level documents; `tools/` excluded). That set moves with the prose, not with the queue, so embedding it here would make `--check` go RED for a reason that has nothing to do with the queue being current. It is reported on demand: `python3 tools/queue_index.py --outside`.
@@ -1189,17 +1191,30 @@ The block below is the parse this document renders, byte for byte. `--check` com
"title": "**Q117 \u2014 OPEN (zeph lane by authorship; opened 2026-10-28 by the pipe, at `f17c936`). A full value invented in one of our own replies counts as a `beae0b1f` recovery, so the checker's live census \u2026"
},
{
"bytes": 9107,
"end_line": 13283,
"bytes": 9108,
"end_line": 13284,
"id": "Q111",
"kind": "record",
"line": 13279,
"lines": 5,
"lines": 6,
"role": "continuation",
"role_detail": "DONE",
"status": null,
"status_line": null,
"title": "**Q111 \u2014 DONE at `a6491d7` (`wizard-work/beam/weighted_interval_scheduling.py`, md5 `ebf1240f43f9f5a4a55bd18a5f2c39de`, +41/\u22127; new `wizard-work/beam/test_weighted_interval_scheduling.py`, md5 \u2026"
},
{
"bytes": 2298,
"end_line": 13285,
"id": "Q118",
"kind": "record",
"line": 13285,
"lines": 1,
"role": "record",
"role_detail": "BOLD-LEAD",
"status": null,
"status_line": null,
"title": "**Q118 \u2014 OPEN (pipe tooling; opened 2026-10-28 by the pipe, per reply 147 \u00a70.1; no lane owns the monitor, it lives outside the repo at `/root/.hermes/scripts/troupe_pipe_monitor.py`). The pipe's own \u2026"
}
],
"ids_multi_section": {
@@ -3547,17 +3562,30 @@ The block below is the parse this document renders, byte for byte. `--check` com
"title": "**Q117 \u2014 OPEN (zeph lane by authorship; opened 2026-10-28 by the pipe, at `f17c936`). A full value invented in one of our own replies counts as a `beae0b1f` recovery, so the checker's live census \u2026"
},
{
"bytes": 9107,
"end_line": 13283,
"bytes": 9108,
"end_line": 13284,
"id": "Q111",
"kind": "record",
"line": 13279,
"lines": 5,
"lines": 6,
"role": "continuation",
"role_detail": "DONE",
"status": null,
"status_line": null,
"title": "**Q111 \u2014 DONE at `a6491d7` (`wizard-work/beam/weighted_interval_scheduling.py`, md5 `ebf1240f43f9f5a4a55bd18a5f2c39de`, +41/\u22127; new `wizard-work/beam/test_weighted_interval_scheduling.py`, md5 \u2026"
},
{
"bytes": 2298,
"end_line": 13285,
"id": "Q118",
"kind": "record",
"line": 13285,
"lines": 1,
"role": "record",
"role_detail": "BOLD-LEAD",
"status": null,
"status_line": null,
"title": "**Q118 \u2014 OPEN (pipe tooling; opened 2026-10-28 by the pipe, per reply 147 \u00a70.1; no lane owns the monitor, it lives outside the repo at `/root/.hermes/scripts/troupe_pipe_monitor.py`). The pipe's own \u2026"
}
],
"nested": [
@@ -3821,6 +3849,15 @@ The block below is the parse this document renders, byte for byte. `--check` com
"refs": 2,
"section": "Q96",
"shape": "BULLET+BOLD"
},
{
"first_mention": 13285,
"form": "BOLD-LEAD",
"id": "Q118",
"line": 13285,
"refs": 1,
"section": "Q111",
"shape": "BULLET+BOLD"
}
],
"preamble": {
@@ -3828,9 +3865,9 @@ The block below is the parse this document renders, byte for byte. `--check` com
"end_line": 8,
"line": 1
},
"queue_bytes": 2012306,
"queue_lines": 13283,
"queue_sha256": "4480217276e0c081f2d8f8b3fc4e11655222df3a301c48608f2a6f138bcb6e27",
"queue_bytes": 2014605,
"queue_lines": 13285,
"queue_sha256": "ae463c1554cb7e372f70d97e8f662edaa9b2aa8064b0d748407d95d4dfaa3e55",
"sections": [
{
"bytes": 3139,