Skip to content

Conversation

@bjp232004
Copy link
Contributor

@bjp232004 bjp232004 commented Jul 24, 2024

…o see data on screen

Summary by CodeRabbit

  • New Features

    • Introduced improved error message handling for the search functionality, enhancing user feedback.
    • Added conditional rendering in the search results to display specific error messages when applicable.
  • Bug Fixes

    • Resolved issues with persistent error messages across searches, ensuring previous errors do not carry over.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 24, 2024

Walkthrough

The changes enhance error management within the useLogs composable and its associated SearchResult component. A new property, countErrorMsg, is introduced to specifically handle error messages related to event counting, improving the clarity of error feedback to users. The UI is updated to display these error messages distinctly, ensuring users are informed about issues during search operations.

Changes

Files Change Summary
web/src/composables/useLogs.ts Introduced countErrorMsg for error handling, ensuring previous messages do not persist. Refactored error handling logic to differentiate counting errors.
web/src/plugins/logs/SearchResult.vue Added conditional rendering for displaying countErrorMsg to enhance user feedback on search errors.

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>.
    • 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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.

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

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.

@github-actions github-actions bot added the ☢️ Bug Something isn't working label Jul 24, 2024
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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3482e5c and 3aee251.

Files selected for processing (2)
  • web/src/composables/useLogs.ts (6 hunks)
  • web/src/plugins/logs/SearchResult.vue (1 hunks)
Additional comments not posted (5)
web/src/plugins/logs/SearchResult.vue (1)

27-33: LGTM! But verify the usage of countErrorMsg in the codebase.

The code changes are approved. The added conditional rendering block improves user feedback by displaying error messages related to event counting.

However, ensure that countErrorMsg is correctly set and used throughout the codebase.

Verification successful

Verified: The usage of countErrorMsg is properly set and used throughout the codebase.

The countErrorMsg is initialized and managed correctly within the useLogs.ts file, and it is referenced appropriately in the SearchResult.vue component.

  • web/src/composables/useLogs.ts
  • web/src/plugins/logs/SearchResult.vue
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of `countErrorMsg` in the codebase.

# Test: Search for the usage of `countErrorMsg`. Expect: Proper setting and usage of `countErrorMsg`.
rg --type python --type vue --type ts --type js 'countErrorMsg'

Length of output: 94


Script:

#!/bin/bash
# Description: Verify the usage of `countErrorMsg` in the codebase.

# Test: Search for the usage of `countErrorMsg`. Expect: Proper setting and usage of `countErrorMsg`.
rg --type vue --type ts --type js 'countErrorMsg'

Length of output: 77


Script:

#!/bin/bash
# Description: Verify the usage of `countErrorMsg` in the codebase.

# Test: Search for the usage of `countErrorMsg`. Expect: Proper setting and usage of `countErrorMsg`.
rg --type ts --type js 'countErrorMsg'

Length of output: 931

web/src/composables/useLogs.ts (4)

137-137: Initialization of countErrorMsg in defaultObject looks good.

This ensures that the property is always defined, preventing potential undefined errors.


372-372: Resetting countErrorMsg in resetQueryData is appropriate.

This ensures that any previous error messages related to event counting are cleared when the query data is reset.


1814-1814: Clearing countErrorMsg in getPageCount is appropriate.

This ensures that any previous error messages are removed, providing a clean state for the new query.


Line range hint 1874-1898:
Setting countErrorMsg with error details in getPageCount enhances error clarity.

This improves clarity by distinguishing between general error messages and those specifically related to counting events.

@bjp232004 bjp232004 merged commit c56b2a0 into main Jul 24, 2024
@bjp232004 bjp232004 deleted the logs-page-page-count-request-failed branch July 24, 2024 12:24
abvarun226 pushed a commit to abvarun226/openobserve that referenced this pull request Aug 8, 2024
openobserve#4044)

…o see data on screen

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **New Features**
- Introduced improved error message handling for the search
functionality, enhancing user feedback.
- Added conditional rendering in the search results to display specific
error messages when applicable.

- **Bug Fixes**
- Resolved issues with persistent error messages across searches,
ensuring previous errors do not carry over.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

☢️ Bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants