You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
shape_materialize.py and bump-leg.py: a row holds YAML_NOT_TEXT_RE's exponents of two or more digits, the no-origin refusal for a tag the leg holds is true, and an else nothing reaches is gone (#1090's review follow-ups) #1103
Goal: the three things rv1090's review of #1090 (#912) left. Add a row that holds YAML_NOT_TEXT_RE's exponents of two or more digits, make one bump refusal true where the leg has no origin, and remove an else nothing reaches.
When it lands. Under Brett Heap's ruling of 2026-10-21T10:32:04Z ("leave the follow-ups out of v1.2.0"), this lands after the v1.2.0 tag.
Line numbers are at d5389eb6.
What happens
No row has an exponent of two or more digits (the review's SHOULD).
Where:YAML_NOT_TEXT_RE at scripts/shape_materialize.py:542-543, and YAML_FLOATS at tests/test_neutral_pin_entry_one_spelling.py:92.
The mutant that survives (R2): change [0-9]+ to [0-9] in both of the rule's exponent groups. All 180 spelling and entry rows still pass.
What it would ship:--pin .5e-10@<sha>, .05E-12 and .5_e-10 written bare. PyYAML reads them as 5e-11, 5e-14 and 5e-11, and --pin accepts all three names.
Why no row catches it: every exponent in YAML_FLOATS has one digit, and PIN_NAMES stops at three characters, too short to hold .5e-10.
One bump refusal is untrue where the leg has no remote named origin (a NIT), at scripts/bump-leg.py:1263.
The case:--to is a tag id that the leg holds without its commit.
What it says:bump-leg-commit-not-on-remote: <tag id> is not in the leg's own object store. But the tag object is in the store.
How it was measured:_unreachable_refusal(..., fetched=False, has_origin=False) called on a clone that lacks the commit.
CLAIMED — lane openRepoShape-5, session 50cede29-ab82-4ca3-9f67-d98e1a58c8d2@Eagle, 2026-10-21T13:59:02Z, for #1103
Logged in lanes/log/openRepoShape-5.md at 6e769578867177dedc6ea752257c27e1e75fd718.
The three reads (lane-collision-protocol Rule 1):
1. existing `CLAIMED —` comments on opensoft/openRepoShape#1103:
none
2. `gh pr list --repo opensoft/openRepoShape --state all --search "#1103"`, kept where the row or its body names `#1103`:
1090 shape_materialize.py, adopt-project.py and bump-leg.py: a tag a clone holds without its commit is one it cannot answer for, `check` says a commit it cannot ask was not asked, and a pinned product YAML 1.1 or 1.2 reads as no text is quoted (#912) fix/912-pin-questions MERGED
3. `git ls-remote --heads git@github.com:opensoft/openRepoShape` branches naming `1103` as a whole token:
none
Activity
shape_materialize.py, adopt-project.py and bump-leg.py: a tag a clone…
brettheap commentedon Oct 21, 2026
CLAIMED — lane openRepoShape-5, session 50cede29-ab82-4ca3-9f67-d98e1a58c8d2@Eagle, 2026-10-21T13:59:02Z, for #1103
Logged in
lanes/log/openRepoShape-5.mdat6e769578867177dedc6ea752257c27e1e75fd718.The three reads (lane-collision-protocol Rule 1):
bump-leg.py: a held tag that leads through a tag the leg lacks names …
docs/release-notes/v1.2.0.md: the fix round on #1155's four section r…
bump-leg.py: `tag_chain_end` builds its header in a dict comprehensio…