feat(tri): window, was the base you measured still the tip - #3380
Merged
Conversation
added 2 commits
September 6, 2026 15:20
69 merges landed on master in 24 hours here, one every 21 minutes, while a corpus measurement takes 15-30. The base moves during almost every measurement, and two failures follow: a delta that is a neighbour's work, and a defect that was repaired upstream while it was being fixed here. Both are one question. Census re-blessed in this same commit: `fetches` moved `files read` by one, which is this commit's own new file cli/tri/src/window.rs.
gHashTag
enabled auto-merge (squash)
September 6, 2026 08:21
Contributor
Contributor
|
📓 NotebookLM Notebook linked to this PR
This notebook contains session context, decisions, and artifacts for this work. |
gHashTag
pushed a commit
that referenced
this pull request
Sep 6, 2026
The squash of #3380 put this branch's own parent content on master as an unrelated commit, so all ten regions conflicted. Resolved to this branch's version after checking it is a superset: the thirteen lines only master had are exactly the ones these fixes replace -- `&recorded[..12]` and the hardcoded `fetch origin`.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #3379
origin/mastertook 69 merges in 24 hours here — one every 21 minutes — while a corpus measurement takes 15-30: build a pinned binary from the base, run 650 specs, build the change, run 650 again. The base moves during almost every measurement, and two failures in one night follow from that one fact.338 → 352, +14became +0 when the base was rebuilt at report time357 → 360, +3was already on master at merge time, both shapes, all three specs greenThe second is the instructive one:
tri loop claimhad been taken before the work started, which is the right order. It did not help, because the neighbour took none. A claim separates two sessions only when both take one.Counted with
--first-parent, deliberately: a three-merge move measured 7 without it, because the range holds every commit of every side branch pulled in, four of them merges. The reader's question is how many pull requests landed — three.Six controls, one per claim. The one worth naming asserts that a window which cannot be read is not a window that did not move: an unresolvable ref gives
None, never zero. Four unit tests. The record lives beside the git dir, not in the worktree, so it cannot reach a commit — asserted too.Also spooled: a skill lesson on the one-sided claim, via
tri skill add.