main · last commit
6 hours ago ·
ti41arbu
sr-ht-dolt-2wo The detail and milestone projections drop the truncation signal
Past Stand
bd reopen sr-ht-dolt-2wo
| Created by | Eugene Blikh |
| Owner | bigbes@gmail.com |
| Created | 2026-08-13T06:05:05Z |
| Started | 2026-08-13T07:08:28Z |
| Updated | 2026-08-13T07:17:39Z |
| Closed | 2026-08-13T07:17:39Z |
beads.Build's detail branch never sets Data.Truncated and BuildMilestones discards the table totals with _, so on a tracker larger than beads.Max (2000 rows) an id in the tail reads as simply absent and a milestone rollup is computed over the first 2000 rows — with nothing saying so. The board path does report its clip; these two do not. Found while building the MCP get_issue and list_milestones tools (e4bc922), which cannot detect it without a second row read and state the limitation in a package comment instead.
Return the totals from those two entry points the way the board path already does, and let both surfaces render them. The alternative — each surface re-reading to check — is the second reading of the schema the beads package exists to prevent.
A fixture tracker past the cap: get_issue on a tail id says the read was clipped rather than claiming the issue does not exist; a milestone rollup over a clipped read is marked.
No outgoing dependencies.
Nothing depends on this issue.
| id | sr-ht-dolt-2wo |
| content_hash | a033adbfe134dfe67605d81f37366dc2f9160455e78098614617bb45320d2d91 |
| title | The detail and milestone projections drop the truncation signal |
| description | beads.Build's detail branch never sets Data.Truncated and BuildMilestones discards the table totals with _, so on a tracker larger than beads.Max (2000 rows) an id in the tail reads as simply absent and a milestone rollup is computed over the first 2000 rows — with nothing saying so. The board path does report its clip; these two do not. Found while building the MCP get_issue and list_milestones tools (e4bc922), which cannot detect it without a second row read and state the limitation in a package comment instead. |
| design | Return the totals from those two entry points the way the board path already does, and let both surfaces render them. The alternative — each surface re-reading to check — is the second reading of the schema the beads package exists to prevent. |
| acceptance_criteria | A fixture tracker past the cap: get_issue on a tail id says the read was clipped rather than claiming the issue does not exist; a milestone rollup over a clipped read is marked. |
| notes | |
| status | closed |
| priority | 2 |
| issue_type | bug |
| assignee | NULL |
| estimated_minutes | NULL |
| created_at | 2026-08-13T06:05:05Z |
| created_by | Eugene Blikh |
| owner | bigbes@gmail.com |
| updated_at | 2026-08-13T07:17:39Z |
| closed_at | 2026-08-13T07:17:39Z |
| closed_by_session | |
| external_ref | NULL |
| spec_id | |
| compaction_level | 0 |
| compacted_at | NULL |
| compacted_at_commit | NULL |
| original_size | NULL |
| sender | |
| ephemeral | 0 |
| wisp_type | |
| pinned | 0 |
| is_template | 0 |
| mol_type | |
| work_type | |
| source_system | |
| metadata | �{} |
| source_repo | |
| close_reason | Landed in ebbd30f: Truncated/ShownOf are now set in every mode (no new fields, no changed meanings), plus IssuesClipped/Missing/MissingBeyondCap so a surface can tell 'no such issue' from 'not in the rows I read'. Fixture clips through a seam that honours limit rather than lowering Max. |
| event_kind | |
| actor | |
| target | |
| payload | |
| await_type | |
| await_id | |
| timeout_ns | 0 |
| waiters | |
| hook_bead | |
| role_bead | |
| agent_state | |
| last_activity | NULL |
| role_type | |
| rig | |
| due_at | NULL |
| defer_until | NULL |
| no_history | 0 |
| started_at | 2026-08-13T07:08:28Z |
| is_blocked | 0 |
| id | 019ff9b9-679b-75b1-96a5-e51b98c0bada |
| issue_id | sr-ht-dolt-2wo |
| event_type | created |
| actor | Eugene Blikh |
| old_value | |
| new_value | |
| comment | NULL |
| created_at | 2026-08-13T09:05:05Z |
| id | 019ff9f3-6e8e-795a-8ccb-15a7e7e6495c |
| issue_id | sr-ht-dolt-2wo |
| event_type | status_changed |
| actor | Eugene Blikh |
| old_value | {"id":"sr-ht-dolt-2wo","title":"The detail and milestone projections drop the truncation signal","description":"beads.Build's detail branch never sets Data.Truncated and BuildMilestones discards the table totals with _, so on a tracker larger than beads.Max (2000 rows) an id in the tail reads as simply absent and a milestone rollup is computed over the first 2000 rows — with nothing saying so. The board path does report its clip; these two do not. Found while building the MCP get_issue and list_milestones tools (e4bc922), which cannot detect it without a second row read and state the limitation in a package comment instead.","design":"Return the totals from those two entry points the way the board path already does, and let both surfaces render them. The alternative — each surface re-reading to check — is the second reading of the schema the beads package exists to prevent.","acceptance_criteria":"A fixture tracker past the cap: get_issue on a tail id says the read was clipped rather than claiming the issue does not exist; a milestone rollup over a clipped read is marked.","status":"open","priority":2,"issue_type":"bug","owner":"bigbes@gmail.com","created_at":"2026-08-13T06:05:05Z","created_by":"Eugene Blikh","updated_at":"2026-08-13T06:05:05Z"} |
| new_value | {"status":"in_progress"} |
| comment | NULL |
| created_at | 2026-08-13T10:08:28Z |
| id | 019ff9fb-d5a7-74a7-9cc0-9241bfb0b101 |
| issue_id | sr-ht-dolt-2wo |
| event_type | closed |
| actor | Eugene Blikh |
| old_value | |
| new_value | Landed in ebbd30f: Truncated/ShownOf are now set in every mode (no new fields, no changed meanings), plus IssuesClipped/Missing/MissingBeyondCap so a surface can tell 'no such issue' from 'not in the rows I read'. Fixture clips through a seam that honours limit rather than lowering Max. |
| comment | NULL |
| created_at | 2026-08-13T10:17:38Z |
No comments.
Close reason