stacks-network/stacks-core

Signer should return exit code 0 when run with no args

Open

#6,558 opened on Oct 2, 2025

View on GitHub
 (2 comments) (0 reactions) (1 assignee)Rust (758 forks)auto 404
choregood first issue

Repository metrics

Stars
 (3,063 stars)
PR merge metrics
 (PR metrics pending)

Description

stacks-signer when run with no args simply displays a help message, and then exits with code '2'.

However, when using an arg like --help or --version, simialr output is displayed and the exit code is 0 (expected).

the exit code of 2 makes it challenging to check the binary is there in some helper scripts:

$ stacks-signer > /dev/null 2&>1; echo $?
2
$ stacks-node > /dev/null 2&>1; echo $?
0

Propose that if no args are defined, keep behavious as it is today but return an exit code of 0

Contributor guide

Research direction
Locate the code in the stacks signer binary where the exit code is set to 2 when no arguments are provided, and change it to 0.
Tech stack
rust
Domain
cli
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rust basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80