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

revert: test(client) wrap cmd.SetArgs to fix bugs for cmd.SetArgs (#18876) #18902

Merged
merged 5 commits into from
Jan 3, 2024

Conversation

levisyin
Copy link
Contributor

This reverts commit ae19acc. #18876

Description

I just found the bug of the implementation of SetArgs in internal/testutil, it would get unexpected default value when the flag field type is SliceValue(Append instead of replace). See detail info in comment.

If spf13/cobra won't support for Reset() error feature, I will choose another way to implement this. But for now, I think it would be better to revert commit first.

Sorry about this, I didn't cover a full test for wrapped SetArgs.

@levisyin levisyin requested a review from a team as a code owner December 27, 2023 09:44
Copy link
Contributor

coderabbitai bot commented Dec 27, 2023

Walkthrough

The overall change involves updating a Go test file to refine how command arguments are set for testing. The update replaces an internal utility function with a command method for argument handling and makes adjustments to flag settings. These changes are aimed at improving the test setup for a specific command function without altering any public or exported entities.

Changes

File Path Change Summary
client/keys/show_test.go Replaced internaltestutil.SetArgs with cmd.SetArgs and updated flag handling for runShowCmd tests.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

Tips

Chat with CodeRabbit Bot (@coderabbitai)

Note: Auto-reply has been disabled for this repository by the repository owner. The CodeRabbit bot will not respond to your comments unless it is explicitly tagged.

  • You can tag CodeRabbit on specific lines of code or entire files in the PR by tagging @coderabbitai in a comment. Examples:
    • @coderabbitai generate unit tests for this file.
    • @coderabbitai modularize this function.
  • You can tag @coderabbitai in a PR comment and ask questions about the PR and the codebase. Examples:
    • @coderabbitai generate interesting stats about this repository from git and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit tests.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid.
    • @coderabbitai read the files in the src/scheduler package and generate README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • The JSON schema for the configuration file is available here.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

@github-actions github-actions bot added C:CLI C:Keys Keybase, KMS and HSMs labels Dec 27, 2023
@julienrbrt julienrbrt changed the title Revert: test(client) wrap cmd.SetArgs to fix bugs for cmd.SetArgs (#18876) revert: test(client) wrap cmd.SetArgs to fix bugs for cmd.SetArgs (#18876) Dec 28, 2023
Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, so we are waiting for changes in cobra instead, if i understand correctly right?

@levisyin
Copy link
Contributor Author

Ok, so we are waiting for changes in cobra instead, if i understand correctly right?

Yep, I will try my best to promote it. If spf13/cobra won't accept it, I will try my best to find another convenient way to wrap the SetArgs.

@atheeshp atheeshp added this pull request to the merge queue Jan 3, 2024
Merged via the queue into cosmos:main with commit 77cbb3c Jan 3, 2024
55 of 57 checks passed
@levisyin levisyin deleted the revert/setargs branch January 3, 2024 07:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C:CLI C:Keys Keybase, KMS and HSMs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants