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

refactor: Use HybridResolver instead of protoregistry.GlobalFiles in runtime/v2/manager #22744

Merged
merged 2 commits into from
Dec 4, 2024

Conversation

hieuvubk
Copy link
Contributor

@hieuvubk hieuvubk commented Dec 4, 2024

Description

Closes: #22688 #22651

  • #22673 not actually solve the root issue. Just overwrite x/account msg & query after registing failed
  • x/accounts.Msg & x/gov.Query is missing from protoregistry.GlobalFiles => use gogoproto.HybridResolver can solve problem

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...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

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.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features

    • Enhanced service registration logic for improved module integration.
  • Bug Fixes

    • Removed deprecated query and message handler functions to streamline account module functionality.
  • Refactor

    • Updated service registration methods to utilize a new resolver type for better error handling and service descriptor management.

Copy link
Contributor

coderabbitai bot commented Dec 4, 2024

📝 Walkthrough

Walkthrough

The pull request introduces significant changes to the service registration logic within the Cosmos SDK's module manager. Key modifications include the removal of the protoregistry import and the transition to using gogoproto.HybridResolver for service registration. Additionally, the configurator struct's registry field type has been updated to align with this new resolver. In the x/accounts/module.go file, the RegisterQueryHandlers and RegisterMsgHandlers functions have been removed, indicating a shift away from the previous handler registration approach.

Changes

File Change Summary
runtime/v2/manager.go - Removed import for protoregistry.
- Updated registerServices to use gogoproto.HybridResolver instead of protoregistry.GlobalFiles.
- Changed registry field type in configurator from *protoregistry.Files to gogoproto.Resolver.
- Updated RegisterService method for compatibility with new resolver.
x/accounts/module.go - Removed functions RegisterQueryHandlers and RegisterMsgHandlers from AppModule.

Assessment against linked issues

Objective Addressed Explanation
Verify service registration in runtime/v2 (#22688)

Possibly related PRs

Suggested labels

C:server/v2, C:x/accounts, C:server/v2 api, backport/v0.52.x

Suggested reviewers

  • sontrinh16
  • kocubinski
  • testinginprod
  • julienrbrt

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.

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.

@hieuvubk hieuvubk requested a review from alpe December 4, 2024 08:43
@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Dec 4, 2024
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.

that makes sense! good catch

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: 1

🧹 Outside diff range and nitpick comments (1)
runtime/v2/manager.go (1)

Line range hint 686-689: Prevent potential panic due to unchecked type assertion in RegisterService

The type assertion prefSd.(protoreflect.ServiceDescriptor) may cause a panic if prefSd does not implement protoreflect.ServiceDescriptor. It's safer to use an ok check to prevent a potential runtime panic.

Apply this diff to fix the issue:

 func (c *configurator) RegisterService(sd *grpc.ServiceDesc, ss interface{}) {
     // first we check if it's a msg server
     prefSd, err := c.registry.FindDescriptorByName(protoreflect.FullName(sd.ServiceName))
     if err != nil {
         c.err = fmt.Errorf("register service: unable to find protov2 service descriptor: please make sure protov2 API counterparty is imported: %s", sd.ServiceName)
         return
     }

-    if !proto.HasExtension(prefSd.(protoreflect.ServiceDescriptor).Options(), cosmosmsg.E_Service) {
+    sdProto, ok := prefSd.(protoreflect.ServiceDescriptor)
+    if !ok {
+        c.err = fmt.Errorf("prefSd does not implement protoreflect.ServiceDescriptor for service %s", sd.ServiceName)
+        return
+    }
+    if !proto.HasExtension(sdProto.Options(), cosmosmsg.E_Service) {
         err = c.registerQueryHandlers(sd, ss)
         if err != nil {
             c.err = err
         }
     } else {
         err = c.registerMsgHandlers(sd, ss)
         if err != nil {
             c.err = err
         }
     }
 }
📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 99dd55b and ae4249f.

📒 Files selected for processing (2)
  • runtime/v2/manager.go (3 hunks)
  • x/accounts/module.go (0 hunks)
💤 Files with no reviewable changes (1)
  • x/accounts/module.go
🧰 Additional context used
📓 Path-based instructions (1)
runtime/v2/manager.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

🔇 Additional comments (3)
runtime/v2/manager.go (3)

487-489: LGTM: Correct usage of gogoproto.HybridResolver in service registration

Switching to gogoproto.HybridResolver for the registry parameter in registerServices aligns with the PR's objective to address the service registration issue.


620-620: LGTM: Updated registerServices function signature

Updating the registry parameter type to gogoproto.Resolver ensures compatibility with the new resolver and reflects the intended design changes.


673-673: LGTM: Changed configurator.registry field type to gogoproto.Resolver

Modifying the registry field to use gogoproto.Resolver aligns with the updated resolver usage and maintains consistency across the codebase.

Comment on lines +487 to 489
if err := registerServices(module, app, gogoproto.HybridResolver); err != nil {
return err
}
Copy link
Contributor

Choose a reason for hiding this comment

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

💡 Codebase verification

Several non-test files still use protoregistry.GlobalFiles and need to be updated

The following files need to be updated to use gogoproto.HybridResolver instead of protoregistry.GlobalFiles:

  • types/msgservice/validate.go
  • server/mock/app.go
  • runtime/v2/types.go
  • orm/model/ormdb/module.go
  • client/v2/autocli/flag/builder.go

Test files using protoregistry.GlobalFiles should also be reviewed and updated for consistency, though they don't affect runtime behavior.

🔗 Analysis chain

Verify no remaining usages of protoregistry.GlobalFiles

To ensure consistency across the codebase, please verify that all instances of protoregistry.GlobalFiles have been replaced with gogoproto.HybridResolver.

Run the following script to identify any remaining usages:


Let me verify if these usages are in test files or actual implementation code by categorizing them.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Search for any usages of protoregistry.GlobalFiles in the codebase.

# Test: Expect no matches for protoregistry.GlobalFiles
rg 'protoregistry\.GlobalFiles'

Length of output: 1351


Script:

#!/bin/bash
# Check for non-test files containing protoregistry.GlobalFiles
echo "=== Non-test files ==="
rg 'protoregistry\.GlobalFiles' --type go | grep -v '_test.go'

echo -e "\n=== Test files ==="
rg 'protoregistry\.GlobalFiles' --type go | grep '_test.go'

Length of output: 1548

@tac0turtle tac0turtle added this pull request to the merge queue Dec 4, 2024
Merged via the queue into main with commit c47fb8a Dec 4, 2024
82 of 83 checks passed
@tac0turtle tac0turtle deleted the hieu/hybid_resolver branch December 4, 2024 10:06
mergify bot pushed a commit that referenced this pull request Dec 4, 2024
…`runtime/v2/manager` (#22744)

(cherry picked from commit c47fb8a)

# Conflicts:
#	runtime/v2/manager.go
julienrbrt added a commit that referenced this pull request Dec 4, 2024
…#22744) (#22749)

Co-authored-by: Hieu Vu <72878483+hieuvubk@users.noreply.github.com>
Co-authored-by: Julien Robert <julien@rbrt.fr>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release C:x/accounts
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Verify x/accounts v2 gRPC service registration
6 participants