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

allow megavault operator to set default quoting params #2620

Merged
merged 1 commit into from
Nov 27, 2024

Conversation

tqin7
Copy link
Contributor

@tqin7 tqin7 commented Nov 27, 2024

Changelist

[Describe or list the changes made in this PR]

Test Plan

[Describe how this PR was tested (if applicable)]

Author/Reviewer Checklist

  • If this PR has changes that result in a different app state given the same prior state and transaction list, manually add the state-breaking label.
  • If the PR has breaking postgres changes to the indexer add the indexer-postgres-breaking label.
  • If this PR isn't state-breaking but has changes that modify behavior in PrepareProposal or ProcessProposal, manually add the label proposal-breaking.
  • If this PR is one of many that implement a specific feature, manually label them all feature:[feature-name].
  • If you wish to for mergify-bot to automatically create a PR to backport your change to a release branch, manually add the label backport/[branch-name].
  • Manually add any of the following labels: refactor, chore, bug.

Summary by CodeRabbit

  • New Features

    • Enhanced authority validation for updating default quoting parameters.
    • Expanded test cases to cover both "Gov Authority" and "Operator Authority" scenarios.
  • Bug Fixes

    • Updated error handling for invalid authority to improve clarity.
  • Documentation

    • Improved test structure by explicitly defining operator roles and updating type references.

@tqin7 tqin7 requested a review from a team as a code owner November 27, 2024 17:09
Copy link
Contributor

coderabbitai bot commented Nov 27, 2024

Walkthrough

The changes in this pull request focus on enhancing the authority validation logic within the UpdateDefaultQuotingParams method of the msgServer struct in the keeper package. The method now verifies if the msg.Authority is either a valid authority or matches the retrieved operator parameters. Additionally, the related test file has been updated to reflect these changes, including renaming the types package to vaulttypes, modifying test cases to accommodate the new operator role, and adjusting error handling accordingly.

Changes

File Change Summary
protocol/x/vault/keeper/msg_server_update_default_quoting_params.go - Enhanced authority validation logic in UpdateDefaultQuotingParams method.
- Updated error returned for invalid authority.
protocol/x/vault/keeper/msg_server_update_default_quoting_params_test.go - Renamed types package to vaulttypes.
- Added operator field to test case struct.
- Updated message type and error handling in tests.

Possibly related PRs

Suggested labels

indexer, protocol, proto

Suggested reviewers

  • vincentwschau

🐰 In the vault where we play,
Authorities check every day.
With operators now in sight,
Quoting params feel just right.
Tests are clear, the logic bright,
Hopping forward, what a delight! 🌟


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

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • 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/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (4)
protocol/x/vault/keeper/msg_server_update_default_quoting_params.go (1)

17-26: Consider adding events and improving documentation

A few suggestions to enhance the implementation:

  1. Emit an event when parameters are updated for better observability
  2. Add documentation about the expected format and constraints for the Authority field

Example implementation:

 func (k msgServer) UpdateDefaultQuotingParams(
 	goCtx context.Context,
 	msg *types.MsgUpdateDefaultQuotingParams,
 ) (*types.MsgUpdateDefaultQuotingParamsResponse, error) {
 	ctx := lib.UnwrapSDKContext(goCtx, types.ModuleName)
 	operator := k.GetOperatorParams(ctx).Operator
 
 	// Check if authority is valid (must be a module authority or operator).
 	if !k.HasAuthority(msg.Authority) && msg.Authority != operator {
 		return nil, errorsmod.Wrapf(
 			types.ErrInvalidAuthority,
 			"invalid authority %s",
 			msg.Authority,
 		)
 	}
 
 	if err := k.SetDefaultQuotingParams(ctx, msg.DefaultQuotingParams); err != nil {
 		return nil, err
 	}
+
+	// Emit event for parameter update
+	ctx.EventManager().EmitEvent(
+		sdk.NewEvent(
+			types.EventTypeDefaultQuotingParamsUpdate,
+			sdk.NewAttribute("authority", msg.Authority),
+			sdk.NewAttribute("params", msg.DefaultQuotingParams.String()),
+		),
+	)
 
 	return &types.MsgUpdateDefaultQuotingParamsResponse{}, nil
 }
protocol/x/vault/keeper/msg_server_update_default_quoting_params_test.go (3)

Line range hint 21-79: Consider adding edge cases to strengthen test coverage.

The test cases effectively cover the main scenarios, but consider adding these edge cases:

  1. Empty operator address in genesis
  2. Empty authority in message
  3. Maximum/minimum bounds for QuotingParams values

Would you like me to help generate these additional test cases?


84-96: LGTM! Genesis setup is well-structured.

The genesis configuration correctly sets up the operator params for testing different authority scenarios.

Consider improving readability with consistent indentation:

 tApp := testapp.NewTestAppBuilder(t).WithGenesisDocFn(func() (genesis types.GenesisDoc) {
     genesis = testapp.DefaultGenesis()
     // Set megavault operator.
     testapp.UpdateGenesisDocWithAppStateForModule(
         &genesis,
         func(genesisState *vaulttypes.GenesisState) {
             genesisState.OperatorParams = vaulttypes.OperatorParams{
                 Operator: tc.operator,
             }
         },
     )
     return genesis
 }).Build()

Line range hint 104-108: Consider strengthening error validation.

While the current assertions verify the behavior correctly, consider using errors.Is() instead of ErrorContains() for more precise error type checking:

-require.ErrorContains(t, err, tc.expectedErr)
+require.True(t, errors.Is(err, vaulttypes.ErrInvalidAuthority))
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 3566800 and 37a3495.

📒 Files selected for processing (2)
  • protocol/x/vault/keeper/msg_server_update_default_quoting_params.go (1 hunks)
  • protocol/x/vault/keeper/msg_server_update_default_quoting_params_test.go (3 hunks)
🔇 Additional comments (3)
protocol/x/vault/keeper/msg_server_update_default_quoting_params.go (2)

17-19: LGTM: Context handling and operator retrieval look good

The context unwrapping and operator parameter retrieval are implemented correctly.


20-26: Authority validation logic looks secure, but needs verification

The implementation correctly validates both module authorities and operator authority, with proper error handling.

Let's verify two critical aspects:

✅ Verification successful

Authority validation implementation is secure and properly validated

The implementation is secure for the following reasons:

  • The HasAuthority implementation properly checks against a pre-initialized map of valid authorities
  • The operator address is validated through OperatorParams.Validate() which ensures it's non-empty
  • The operator is initialized securely in genesis with the governance module account as default
  • Changes to operator require proper authority validation through both HasAuthority check and operator match
🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify operator validation and HasAuthority implementation

# Check if operator address is validated when set
ast-grep --pattern 'SetOperatorParams($$$)' 

# Check HasAuthority implementation
ast-grep --pattern 'func ($_) HasAuthority($_) bool {
  $$$
}'

# Look for any tests validating operator address
rg -l "TestSetOperatorParams|TestValidateOperatorAddress" --type go

Length of output: 76625


Script:

#!/bin/bash
# Let's verify the operator validation and initialization

# Check how operator is set and validated
rg -A 5 "SetOperator" --type go

# Check for operator validation in tests
rg -A 5 "TestSetOperator" --type go

# Look for operator initialization in keeper
rg -A 5 "NewKeeper.*operator" --type go

Length of output: 2742


Script:

#!/bin/bash
# Let's verify the operator validation implementation

# Check operator validation in types
rg -A 5 "func.*Validate.*Operator" --type go

# Check operator params validation
cat protocol/x/vault/types/params.go

# Check operator params initialization in genesis
cat protocol/x/vault/types/genesis.go

Length of output: 4718

protocol/x/vault/keeper/msg_server_update_default_quoting_params_test.go (1)

12-14: LGTM! Import changes are appropriate.

The imports are correctly updated to support the new operator validation functionality and package renaming.

@tqin7 tqin7 merged commit 6ca9b4e into main Nov 27, 2024
22 checks passed
@tqin7 tqin7 deleted the tq/operator-default-vault-quoting branch November 27, 2024 19:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants