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 not found error for gateway handler #2726

Merged
merged 1 commit into from
Oct 30, 2024
Merged

Conversation

datelier
Copy link
Contributor

@datelier datelier commented Oct 30, 2024

Description

SSIA

Related Issue

Versions

  • Vald Version: v1.7.13
  • Go Version: v1.23.2
  • Rust Version: v1.81.0
  • Docker Version: v27.3.1
  • Kubernetes Version: v1.31.1
  • Helm Version: v3.16.2
  • NGT Version: v2.2.4
  • Faiss Version: v1.9.0

Checklist

Special notes for your reviewer

Summary by CodeRabbit

  • Bug Fixes

    • Improved error handling in MultiUpdate and MultiRemove methods for better error reporting.
    • Enhanced error logging for clearer traceability of issues.
  • Refactor

    • Streamlined error handling logic for improved readability and maintainability.

@datelier datelier requested review from a team, kmrmt and vankichi and removed request for a team October 30, 2024 04:43
Copy link
Contributor

coderabbitai bot commented Oct 30, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request focus on enhancing error handling and logging within the pkg/gateway/lb/handler/grpc/handler.go file. Key improvements include refined error aggregation in the MultiUpdate and MultiRemove methods, standardized error logging using a consistent variable, and minor refactoring for better readability and maintainability. The overall functionality remains unchanged, ensuring that the methods still perform their intended operations while providing clearer and more reliable error reporting.

Changes

File Path Change Summary
pkg/gateway/lb/handler/grpc/handler.go - Enhanced error handling in MultiUpdate and MultiRemove methods.
- Standardized error logging using the errs variable.
- Minor refactoring for improved readability and maintainability.

Possibly related PRs

Suggested labels

priority/low, area/gateway/lb, type/refactoring

Suggested reviewers

  • hlts2
  • kpango

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.

@vdaas-ci
Copy link
Collaborator

[CHATOPS:HELP] ChatOps commands.

  • 🙆‍♀️ /approve - approve
  • 🍱 /format - format codes and add licenses
  • /gen-test - generate test codes
  • 🏷️ /label - add labels
  • 🔚 2️⃣ 🔚 /label actions/e2e-deploy - run E2E deploy & integration test

Copy link

codecov bot commented Oct 30, 2024

Codecov Report

Attention: Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.

Project coverage is 23.93%. Comparing base (46d05fc) to head (c42ceaa).
Report is 3 commits behind head on main.

Files with missing lines Patch % Lines
pkg/gateway/lb/handler/grpc/handler.go 0.00% 6 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2726      +/-   ##
==========================================
- Coverage   23.95%   23.93%   -0.02%     
==========================================
  Files         545      545              
  Lines       54324    54322       -2     
==========================================
- Hits        13011    13001      -10     
- Misses      40538    40544       +6     
- Partials      775      777       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 91518e5 and c42ceaa.

📒 Files selected for processing (1)
  • pkg/gateway/lb/handler/grpc/handler.go (2 hunks)
🧰 Additional context used
🪛 GitHub Check: codecov/patch
pkg/gateway/lb/handler/grpc/handler.go

[warning] 1907-1907: pkg/gateway/lb/handler/grpc/handler.go#L1907
Added line #L1907 was not covered by tests


[warning] 1909-1909: pkg/gateway/lb/handler/grpc/handler.go#L1909
Added line #L1909 was not covered by tests


[warning] 1911-1911: pkg/gateway/lb/handler/grpc/handler.go#L1911
Added line #L1911 was not covered by tests


[warning] 2737-2737: pkg/gateway/lb/handler/grpc/handler.go#L2737
Added line #L2737 was not covered by tests


[warning] 2739-2739: pkg/gateway/lb/handler/grpc/handler.go#L2739
Added line #L2739 was not covered by tests


[warning] 2741-2741: pkg/gateway/lb/handler/grpc/handler.go#L2741
Added line #L2741 was not covered by tests

🔇 Additional comments (1)
pkg/gateway/lb/handler/grpc/handler.go (1)

2737-2741: 🛠️ Refactor suggestion

Add test coverage and consider refactoring error handling.

The error handling logic is correct but lacks test coverage. Additionally, there's an opportunity to reduce code duplication:

  1. Add test cases for error scenarios in MultiRemove
  2. Consider extracting the common error handling pattern with span recording into a helper function, as this pattern is repeated in both MultiUpdate and MultiRemove methods.

Example helper function:

func (s *server) recordErrorSpan(span trace.Span, err error) {
    if st, _ := status.FromError(err); st != nil && span != nil {
        span.RecordError(err)
        span.SetAttributes(trace.FromGRPCStatus(st.Code(), st.Message())...)
        span.SetStatus(trace.StatusError, err.Error())
    }
}
🧰 Tools
🪛 GitHub Check: codecov/patch

[warning] 2737-2737: pkg/gateway/lb/handler/grpc/handler.go#L2737
Added line #L2737 was not covered by tests


[warning] 2739-2739: pkg/gateway/lb/handler/grpc/handler.go#L2739
Added line #L2739 was not covered by tests


[warning] 2741-2741: pkg/gateway/lb/handler/grpc/handler.go#L2741
Added line #L2741 was not covered by tests

pkg/gateway/lb/handler/grpc/handler.go Show resolved Hide resolved
@kmrmt kmrmt merged commit 467ab10 into main Oct 30, 2024
73 of 76 checks passed
@kmrmt kmrmt deleted the bugfix/gateway/fix-not-found branch October 30, 2024 05:22
vdaas-ci pushed a commit that referenced this pull request Oct 30, 2024
vankichi pushed a commit that referenced this pull request Oct 30, 2024
Co-authored-by: datelier <57349093+datelier@users.noreply.github.com>
takuyaymd pushed a commit to takuyaymd/vald that referenced this pull request Dec 2, 2024
takuyaymd pushed a commit to takuyaymd/vald that referenced this pull request Dec 2, 2024
This was referenced Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants