Skip to content

[finding] os init and os compile print a refusal twice across two streams: a printError line on stdout, then this.error re-renders the same sentence as oclif's Error block on stderr #21542

Description

@objectstack-fleet

Filing gate: ① a defect with a named position, a finding of class (a).

What happens (measured, public door)

os init demo -t bogus prints ✗ Unknown template: bogus on stdout, then oclif's › Error: Unknown template: bogus on stderr, and exits 2. One refusal's sentence is read twice, across two streams.

Why (read from source at origin/main)

Direction (⛔ not a ruling)

One rendering per refusal, by the split #15692 established. Either the command prints the ✗ line and raises with this.exit(n), or it raises with this.error and prints nothing itself, or it uses the isReportedError shape. ⛔ No second mechanism. Pins: each of the 8 refusals renders its sentence once at the public door, with its exit status unchanged.

Dedupe

MCP search_issues, repo-scoped, open and closed: 「printError then this.error refusal printed twice stdout stderr oclif Error block」 gave 1 hit, #21523, which is the exit-signal re-report from a catch, a different mechanism. None covers this.

Dedupe words: printError then this.error; os init refusal printed twice stdout stderr; oclif Error block repeats the ✗ line; Unknown template printed twice.


Generated by Claude Code

Activity

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

Metadata

Metadata

Assignees

Labels

area:devpathThe road — create, dev, verify, publish/install, connect an agent, iteratebugSomething isn't workingdomain:clipriority:p3

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions