A failed push in phase-pr writes the pre-push hook's whole output into the review-state card message #586
Labels
No labels
agent-ready
bug
contract
documentation
duplicate
enhancement
good first issue
help wanted
invalid
needs-human
needs-input
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
iterative-works/iw-cli#586
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Found during IW-578 phase 1.
A failed push in
phase-prwrites the whole failure text — the pre-push hook's full output, ~600 KB — into the review-state card'smessagefield.Seen again on IW-491 phase 1: the first
phase-pr --no-waitpush failed, and the card grew to 623 KB, withmessageat 516 KB.Seen again during IW-652:
iw phase-prwrites the whole output of a push that the pre-push hook refused (about 600 KB of test log) into the review-statemessage, and the text stays after a later green run — PR #664, review-state.json after the run that was stopped byCommandDeclarationTest.Seen again in IW-715 (2026-10-05):
message, and later commands keep it — core/adapters/Git.scala:287 puts$reason(all of stderr) into the error, and phase-pr stores it; on 2026-10-05 the IW-715 card grew to 700 KB (message580 385 chars), still there after phase-advance, so everyreview-state path/catof the card floods the terminal.Seen again during IW-672, phase 1:
iw phase-prwrites the whole failedgit pushoutput (pre-push hook log, ~470 KB) into review-statemessage— seen on IW-672 phase 1; the card should hold a short summary.Intake: agent-ready
Workflow: diagnostic
Reason: all gates passed
Analysis: project-management/issues/IW-586/analysis.md on branch IW-586
Implement: needs-human
Reason: batch-implement exit 1 — the kanon plugin does not compile against the iw-cli core of this branch.
ForgeCatchUp.scala:143expectsEither[String, …]fromfetchPullRequestForBranch, and the core now returnsEither[TrackerError, …](#778, #780). No phase ran. This stops every iw-cli issue until the plugin is updated, not only this one.The plugin wrote no batch-implement.log. The last lines of the command output:
Release: the implement loop failed this issue for a reason outside it. The kanon plugin did not compile against iw-cli main, because the tracker port now returns TrackerError (iw-cli #778). The plugin fix is dev-docs #484, and iw-cli 0.22.1 carries the core change. The issue goes back to the implement loop.