Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

denom trace CLI doens't contain actual example #1440

Closed
3 tasks
okwme opened this issue May 26, 2022 · 0 comments · Fixed by #1442
Closed
3 tasks

denom trace CLI doens't contain actual example #1440

okwme opened this issue May 26, 2022 · 0 comments · Fixed by #1442
Assignees

Comments

@okwme
Copy link

okwme commented May 26, 2022

Summary of Bug

gaiad q ibc-transfer denom-hash --help results in:

Usage:
  gaiad query ibc-transfer denom-hash [trace] [flags]

Examples:
gaiad query ibc-transfer denom-hash [denom_trace]

...

the example should have an actual example since there is no explanation of what a denom_trace is.
According to the error message:

Error: rpc error: code = InvalidArgument desc = rpc error: code = InvalidArgument desc = trace info must come in pairs of port and channel identifiers '{portID}/{channelID}', got the identifiers: [transfer]: invalid request

it should be {port}/{channel} but it should actually be {port}/{channel}/{denom}. There should be an actual example of a denom_trace.

Version

gaia v7.0.1

Steps to Reproduce


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged/assigned
@crodriguezvega crodriguezvega added this to the Q2-2022-backlog milestone May 26, 2022
@crodriguezvega crodriguezvega moved this to Todo in ibc-go May 26, 2022
@crodriguezvega crodriguezvega moved this from Todo to In review in ibc-go May 26, 2022
@crodriguezvega crodriguezvega self-assigned this May 30, 2022
Repository owner moved this from In review to Done in ibc-go May 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants