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

fix service request query #471

Merged
merged 2 commits into from
Jan 13, 2025
Merged

fix service request query #471

merged 2 commits into from
Jan 13, 2025

Conversation

wangjiulian
Copy link
Collaborator

@wangjiulian wangjiulian commented Jan 9, 2025

Summary by CodeRabbit

  • Refactor
    • Improved code modularity and readability in query processing
    • Simplified message index finding logic in transaction event handling
    • Introduced a new helper function for enhanced error handling and clarity

Copy link

coderabbitai bot commented Jan 9, 2025

Walkthrough

The pull request introduces a refactoring of the QueryRequestContextByTxQuery function in the service client utilities. The primary change involves extracting a complex event searching logic into a new helper function findMsgIndex. This function encapsulates the process of finding a specific message index within transaction logs, improving code modularity and readability by centralizing the event searching and context identification logic.

Changes

File Change Summary
modules/service/client/utils/query.go - Added new helper function findMsgIndex
- Refactored message index searching logic
- Improved error handling for context identification

Poem

🐰 A rabbit's tale of code so neat,
Where loops once danced, now functions meet
Refactored paths, clear and bright
Message index found with pure delight
Simplicity hops, complexity fades away! 🔍

Finishing Touches

  • 📝 Generate Docstrings (Beta)

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 generate docstrings to generate docstrings for this PR. (Beta)
  • @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

@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

🧹 Nitpick comments (4)
modules/service/client/utils/query.go (4)

102-103: Add return value documentation.

Please document the return values in the function comment to clarify the meaning of -1 and possible error conditions.

-// findMsgIndex will find the message index in the txInfo.
+// findMsgIndex finds the message index in the txInfo.
+// Returns the message index (>= 0) if found, or -1 if not found.
+// Returns an error if the context is unknown or if parsing fails.

111-116: Fix potential integer overflow and typo.

The current implementation has two issues:

  1. ParseInt could overflow on 32-bit systems
  2. Variable name has a typo ('paresIndex')
-                        paresIndex, err := strconv.ParseInt(attribute.Value, 10, 64)
-                        if err != nil {
-                            return msgIndex, err
-                        }
-                        msgIndex = int(paresIndex)
+                        parsedIndex, err := strconv.Atoi(attribute.Value)
+                        if err != nil {
+                            return msgIndex, err
+                        }
+                        msgIndex = parsedIndex

104-104: Define constant for sentinel value.

The magic number -1 is used multiple times as a sentinel value. Consider defining it as a constant for better maintainability.

+const msgIndexNotFound = -1
+
 func findMsgIndex(txInfo *sdk.TxResponse, params types.QueryRequestContextRequest) (int, error) {
-    msgIndex := -1
+    msgIndex := msgIndexNotFound
     // ... rest of the function
-    return -1, fmt.Errorf("unknown request context: %s", params.RequestContextId)
+    return msgIndexNotFound, fmt.Errorf("unknown request context: %s", params.RequestContextId)

Also applies to: 130-131, 148-149


133-133: Document version compatibility.

The comment "Compatible with older versions" could be more specific about which versions are supported and why this compatibility is needed.

-    // Compatible with older versions.
+    // Handle logs format from pre-v1.x versions where events were stored in transaction logs
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 96f998e and b199c2b.

📒 Files selected for processing (1)
  • modules/service/client/utils/query.go (2 hunks)
🔇 Additional comments (1)
modules/service/client/utils/query.go (1)

69-72: LGTM! Clean refactoring of message index lookup.

The extraction of the complex event searching logic into findMsgIndex improves code readability while maintaining the same behavior.

modules/service/client/utils/query.go Outdated Show resolved Hide resolved
@wangjiulian wangjiulian changed the title fix request query fix service request query Jan 10, 2025
Copy link

@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

🧹 Nitpick comments (4)
modules/service/client/utils/query.go (4)

112-113: Fix typo in variable name.

The variable name paresIndex appears to be a typo and should be parseIndex.

-                       paresIndex, err := strconv.ParseInt(attribute.Value, 10, 64)
+                       parseIndex, err := strconv.ParseInt(attribute.Value, 10, 64)

108-129: Simplify nested loops with early returns.

The deeply nested loops with multiple conditions can be simplified using early returns. This would improve readability and reduce cognitive complexity.

 if txInfo.Logs == nil {
-    for _, event := range txInfo.Events {
-        if event.Type == types.EventTypeCreateContext {
-            for _, attribute := range event.Attributes {
-                if attribute.Key == types.EventTypeMsgIndex {
-                    parseIndex, err := strconv.ParseInt(attribute.Value, 10, 64)
-                    if err != nil {
-                        return msgIndex, err
-                    }
-                    msgIndex = int(parseIndex)
-                }
-
-                if attribute.Key == types.AttributeKeyRequestContextID &&
-                    attribute.Value == params.RequestContextId {
-                    found = true
-                }
-
-                if found && msgIndex != -1 {
-                    return msgIndex, nil
-                }
-            }
-        }
-    }
+    for _, event := range txInfo.Events {
+        if event.Type != types.EventTypeCreateContext {
+            continue
+        }
+        
+        for _, attribute := range event.Attributes {
+            switch attribute.Key {
+            case types.EventTypeMsgIndex:
+                parseIndex, err := strconv.ParseInt(attribute.Value, 10, 64)
+                if err != nil {
+                    return msgIndex, err
+                }
+                msgIndex = int(parseIndex)
+                if found {
+                    return msgIndex, nil
+                }
+            case types.AttributeKeyRequestContextID:
+                if attribute.Value == params.RequestContextId {
+                    found = true
+                    if msgIndex != -1 {
+                        return msgIndex, nil
+                    }
+                }
+            }
+        }
+    }

134-147: Extract older version compatibility logic into a separate function.

The compatibility logic for older versions should be extracted into a separate function for better maintainability and clarity.

+func findMsgIndexFromLogs(txInfo *sdk.TxResponse, params types.QueryRequestContextRequest) (int, error) {
+    for i, log := range txInfo.Logs {
+        for _, event := range log.Events {
+            if event.Type != types.EventTypeCreateContext {
+                continue
+            }
+            
+            for _, attribute := range event.Attributes {
+                if attribute.Key == types.AttributeKeyRequestContextID &&
+                    attribute.Value == params.RequestContextId {
+                    return i, nil
+                }
+            }
+        }
+    }
+    return -1, fmt.Errorf("unknown request context: %s", params.RequestContextId)
+}

 func findMsgIndex(txInfo *sdk.TxResponse, params types.QueryRequestContextRequest) (int, error) {
     const errUnknownContext = "unknown request context: %s"
     if txInfo.Logs == nil {
         // ... existing direct events logic ...
     }
 
     // Compatible with older versions.
-    for i, log := range txInfo.Logs {
-        // ... existing logs logic ...
-    }
-    return msgIndex, fmt.Errorf(errUnknownContext, params.RequestContextId)
+    return findMsgIndexFromLogs(txInfo, params)
 }

102-150: Add documentation for version compatibility.

The function handles two different versions but lacks documentation explaining when each code path is used. Add comments explaining the version differences and when each path is taken.

+// findMsgIndex searches for the message index in transaction information using two methods:
+// 1. Direct events (newer versions): When txInfo.Logs is nil, searches through txInfo.Events
+// 2. Logs-based events (older versions): When txInfo.Logs is present, searches through the logs
+//
+// The function returns the found message index or -1 with an error if the context is not found.
 func findMsgIndex(txInfo *sdk.TxResponse, params types.QueryRequestContextRequest) (int, error) {
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b199c2b and 9d6e772.

📒 Files selected for processing (1)
  • modules/service/client/utils/query.go (2 hunks)
🔇 Additional comments (1)
modules/service/client/utils/query.go (1)

69-72: Clean refactoring of event search logic!

Good job extracting the complex event searching logic into a separate function. This improves readability and maintainability.

@mitch1024 mitch1024 merged commit 04cdd04 into main Jan 13, 2025
8 checks passed
@mitch1024 mitch1024 deleted the fix/request_context branch January 13, 2025 07:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants