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
the family root's bootstrap.py: git's update killed by a signal (exit 129 and above) gives the credential advice and family bootstrap ok #998
The state:members/IRRS's own .gitmodules gives its code leg a bare branch, a key with no value.
Git:submodule--helper died of signal 11. Its update exits 139 and goes on to IRSS.
Bootstrap (--skip-members): FETCH INCOMPLETE (git exit 139), the credential advice "If the members are PRIVATE, set SHAPE_LEGS_TOKEN ...", and family bootstrap ok, exit 0.
A signal is never a missing credential's. The run should not end ok or give the advice.
The behaviour is already there at #889's 29083a5f, and #954 (#892) does not change it. #954 asks where git stopped only on exit 128 (GIT_DIED), and the issue's lines exit exactly 128. Lane 5 listed this as checklist candidate 1 on #954.
Direction
Where git's update ends by a signal, end the run FAILED, naming the signal and the exit code, with no credential advice. For example: UPDATE KILLED, and not for want of a credential: git's update ended on signal 11 (exit 139).
Two shapes to read:
an exit code above 128, which git gives where a child it ran died of signal N (128 + N);
a negative returncode, where git itself was killed (Python's -N).
P3's state on git 2.43: exit non-zero, the signal named, no advice and no ok.
A portable row, since a newer git may not crash on a bare branch (tests/test_doctor_legs_members_next.py already skips 6 rows where 2.43 crashes on one): a wrapper git first on PATH that runs the real git for everything but submodule update, and for that one exits 139 or kills itself with SIGSEGV. Both shapes are then named, and neither gives the advice.
The credential control (no credential, pin moved on, exit 128) keeps the advice and ok.
Found by lane 5's review of #954 (checklist candidate 1, issuecomment-6253384652). Follows #892 (#954).
CLAIMED — lane openRepoShape-5, session 50cede29-ab82-4ca3-9f67-d98e1a58c8d2@Eagle, 2026-10-20T05:17:51Z, for #998
Logged in lanes/log/openRepoShape-5.md at 30ce8648ed10b21910ac7deae7e072fe6c59e088.
The three reads (lane-collision-protocol Rule 1):
1. existing `CLAIMED —` comments on opensoft/openRepoShape#998:
none
2. `gh pr list --repo opensoft/openRepoShape --state all --search "#998"`, kept where the row or its body names `#998`:
954 the family root's bootstrap.py: a gitlink a member's own index gives no url, or a member's commit that a fetch reaching its remote did not bring, fails the run by name with its cure and no credential advice, where it said `family bootstrap ok` beside git's exit 128 (#892) fix/892-bootstrap-ok-after-128 OPEN
3. `git ls-remote --heads git@github.com:opensoft/openRepoShape` branches naming `998` as a whole token:
none
Activity
brettheap commentedon Oct 20, 2026
CLAIMED — lane openRepoShape-5, session 50cede29-ab82-4ca3-9f67-d98e1a58c8d2@Eagle, 2026-10-20T05:17:51Z, for #998
Logged in
lanes/log/openRepoShape-5.mdat30ce8648ed10b21910ac7deae7e072fe6c59e088.The three reads (lane-collision-protocol Rule 1):
the family root's bootstrap.py: a gitlink a member's own index gives …
the family root's bootstrap.py: git's update ended by a signal fails …
the family root's bootstrap.py: a git that git's update ran dying of …
the family root's bootstrap.py: `credential_advice` and `ended_on` sa…