Skip to content

fix(pp): drop signer field from trigger-resolver autocli flags - #33

Merged
genaris merged 1 commit into
mainfrom
fix/pp-trigger-resolver-autocli
Aug 12, 2026
Merged

genaris merged 1 commit into
mainfrom
fix/pp-trigger-resolver-autocli

Conversation

@pratikasr

Copy link
Copy Markdown
Contributor

veranad tx pp trigger-resolver failed with Error: no such flag - on any
flag combination, including --dry-run.

MsgTriggerResolver declares operator as its cosmos.msg.v1.signer, but the
autocli entry also listed operator in FlagOptions without a Name. client/v2
then records SignerInfo{FlagName: ""}, skips the automatic --from wiring, and
calls MarkFlagRequired("") in RunE — pflag returns no such flag -.

Fix: drop the operator FlagOptions entry so the signer comes from --from,
matching the other pp commands. Checked all 9 modules; only occurrence.

Verified on a local chain: before no such flag -, after code 0 with the
trigger_resolver event emitted.

Closes #32

@pratikasr
pratikasr marked this pull request as ready for review August 11, 2026 18:03
@pratikasr
pratikasr requested a review from genaris August 11, 2026 18:03
@genaris
genaris merged commit 0b52c89 into main Aug 12, 2026
5 checks passed
@genaris
genaris deleted the fix/pp-trigger-resolver-autocli branch August 12, 2026 16:33
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.

tx pp trigger-resolver CLI is broken: "no such flag"

2 participants