Skip to content

bitwalk: --help and a missing file panic instead of printing usage or an error - #6551

Open
gHashTag wants to merge 2 commits into
masterfrom
queen-6039
Open

gHashTag wants to merge 2 commits into
masterfrom
queen-6039

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 5, 2026

Copy link
Copy Markdown
Owner

Closes #6039

Written by a bee on queen-6039 and published by tools/queen/publish.py. The branch itself is the bee's; the second commit is the coordination entry every pull request must add, which a bee has no way to know about.

1 file changed, 221 insertions(+), 99 deletions(-)

🤖 Generated with Claude Code

Trinity Bee and others added 2 commits October 5, 2026 16:13
- Add proper help flag handling (-h/--help/no args) that prints usage and exits 0
- Add unknown flag detection that prints usage and exits 2
- Replace unwrap() calls with proper error handling for file operations
- Use named bools for flag checks as in the rest of the file
- Print error messages in format 'bitwalk: PATH: <error>' and exit 1 on file errors
- Keep walk loop working for bare 'bitwalk FILE...' usage

Closes #6039
A pull request must add exactly one docs/now entry and a bee has no way
to know that: its brief names a boundary file and acceptance criteria,
and docs/now/ is neither. The publisher adds it rather than failing the
gate.

Closes #6039

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-05 16:34:38 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 42
PRs with All Checks Green 8
READY 6
FAILING 42
PENDING 0
NO CHECKS YET 0

These columns do not partition: 6 + 42 + 0 + 0 = 48, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=9f2c8a4829f6 != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

This was referenced Oct 5, 2026
This was referenced Oct 6, 2026
@gHashTag

gHashTag commented Oct 6, 2026

Copy link
Copy Markdown
Owner Author

Triage note (reviewer-bee queue, no review verdict):

Blocking, author-fixable: the bench check fails because specs/xilinx7/bitwalk.rs does not compile. Reproduce with rustc -O --edition 2021 specs/xilinx7/bitwalk.rs -o /tmp/bitwalk. Two errors:

  1. line 748, the usage println!: the text specs/xilinx7/{packets,frames,far}.t27 is read as a format placeholder (python-style braces). Escape it as {{packets,frames,far}}.
  2. line 848: eprintln!("bitwalk: {}", a[2], e); passes two arguments for one placeholder. Make it eprintln!("bitwalk: {} {}", a[2], e); or drop the unused one.

Not your fault, ignore: spec-guards and coverage failed on stale seals of specs/runtime/process.t27 and specs/automation/kanban-card-chat.t27 on master. #6546 re-sealed them at 16:38 UTC, two minutes after this run. A rebase on current main clears them.

What re-queues it: a new push to queen-6039 with the compile fix, ideally rebased on main. tri review queue will pick up the new head. Note this edits an existing Rust file, which the own-language rule allows only with the owner's owner-approved-foreign label.

gHashTag added a commit that referenced this pull request Oct 6, 2026
…oad spends no attempt (Refs #5776)

B34. The two-model rule dead-ended: when z.ai answered 1305 and the CLI fell
back mid-review, the first review's modelUsage held both free flash models and
second_model() found none left, so every such APPROVE ended incomplete -- 29
rows in all, 18 of the 23 incompletes on 2026-10-06.

The CLI (2.1.283) does not alternate: on 1305 it sets mainLoopModel to the
fallback and stays there, so the verdict was written by glm-4.5-flash. The
rule is kept -- two models, each reaching APPROVE on its own from the same
brief -- and the second model now only has to differ from the model that WROTE
the first verdict (verdict_model). It still runs without a fallback.

An agent-failed on 1305 (the second opinion has no fallback) is z.ai's load,
not the head's, and spends no attempt, as B18 made a fallback free: #6551 and
#6730 are reviewable again. The opinion now names the model that wrote it, so
a review that ran wholly on 4.5 no longer reads "glm-4.7-flash approved,
glm-4.7-flash requested changes" (#6759).

Six new self-test checks failed by name on the old code; self-test 0
failures, bees 0, merger gate 0 of 26, loop-tools 0.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bitwalk: --help and a missing file panic instead of printing usage or an error

2 participants