-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
fix: list keys output for empty keys #15876
Conversation
… breaking scripts that expect json output when requesting json output
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tACK.
Do you think it is worth fixing L47 as well to return a JSON with only the names?
Using the -n
flag does not return a JSON (simd keys list -n --output json
)
I am going to merge this now. I let you open a follow-up PR if you think |
(cherry picked from commit 5948b38) # Conflicts: # CHANGELOG.md
@@ -187,6 +187,7 @@ Ref: https://keepachangelog.com/en/1.0.0/ | |||
* (x/capability) [#15030](https://github.com/cosmos/cosmos-sdk/pull/15030) Prevent `x/capability` from consuming `GasMeter` gas during `InitMemStore` | |||
* (types/coin) [#14739](https://github.com/cosmos/cosmos-sdk/pull/14739) Deprecate the method `Coin.IsEqual` in favour of `Coin.Equal`. The difference between the two methods is that the first one results in a panic when denoms are not equal. This panic lead to unexpected behavior | |||
* (x/crypto) [#15258](https://github.com/cosmos/cosmos-sdk/pull/15258) Write keyhash file with permissions 0600 instead of 0555. | |||
* (client/keys) [15867](https://github.com/cosmos/cosmos-sdk/pull/15876) Fix the output of the client keys query when there are no keys |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated the changelog wording here.
It is not significant on main, as this line will get deleted when we release v0.47.2.
…15894) Co-authored-by: Mantas Vidutis <mantas.a.vidutis@gmail.com> Co-authored-by: Julien Robert <julien@rbrt.fr>
Make sure that the expected output format is honored. this println is breaking scripts that expect json output when requesting json output
Description
A recent change caused listing of an empty key set to always print a response string to stdout. This means you can't structure scripts around the keys list query, as requesting json won't return json. This breaks existing code.
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
!
to the type prefix if API or client breaking changeCHANGELOG.md
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
!
in the type prefix if API or client breaking change