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

feat: show estimated rows #22350

Closed
wants to merge 3 commits into from
Closed

feat: show estimated rows #22350

wants to merge 3 commits into from

Conversation

aspicer
Copy link
Contributor

@aspicer aspicer commented May 18, 2024

Show a target of estimated rows

image

Copy link

coderabbitai bot commented May 19, 2024

Walkthrough

The recent update in the EmptyStates.tsx file introduces logic to display estimated rows in the loading state component based on the polling operation's response. This enhancement aims to provide users with a more informative loading experience by showing estimated rows when available.

Changes

File Path Change Summary
frontend/src/scenes/insights/EmptyStates.tsx Added logic to display estimated rows in the loading state component based on polling operation response.

🌸 In the code, a change took flight,
Now loading states are more bright. 🌟
Rows estimated, they now show,
Insight's progress, in a glow.
With each poll, a clearer sight,
Making waiting feel just right.
Hoppity hop, code 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>.
    • 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.

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 a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

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

CodeRabbit Configration 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

Review Details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE

Commits Files that changed from the base of the PR and between af868fb and 6529102.
Files selected for processing (1)
  • frontend/src/scenes/insights/EmptyStates/EmptyStates.tsx (2 hunks)
Additional comments not posted (1)
frontend/src/scenes/insights/EmptyStates/EmptyStates.tsx (1)

121-121: Ensure the calculation for estimatedRows is correct and optimized.

Verification successful

The calculation for estimatedRows appears to be correct and consistent within the codebase. The insightPollResponse, status, and query_progress are properly defined and used in the EmptyStates.tsx file.

  • insightPollResponse is obtained from useValues(insightDataLogic(insightProps)).
  • status and query_progress are accessed correctly from insightPollResponse.

No further issues were found regarding the calculation and usage of estimatedRows.

Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the calculation for `estimatedRows` is correct and optimized.

# Test: Search for similar calculations in the codebase. Expect: Consistent and optimized usage.
rg --type typescript $'insightPollResponse?.status?.query_progress?.estimated_rows_total'

Length of output: 125



Script:

#!/bin/bash
# Description: Verify the calculation for `estimatedRows` is correct and optimized.

# Find all TypeScript files and search for the pattern within those files.
fd --extension ts --exec rg 'insightPollResponse?.status?.query_progress?.estimated_rows_total' {}

Length of output: 102



Script:

#!/bin/bash
# Description: Verify the definitions and usages of `insightPollResponse`, `status`, and `query_progress`.

# Search for the definition and usage of `insightPollResponse`.
rg 'insightPollResponse' --type ts

# Search for the definition and usage of `status` within the context of `insightPollResponse`.
rg 'insightPollResponse.*status' --type ts

# Search for the definition and usage of `query_progress` within the context of `status`.
rg 'status.*query_progress' --type ts

Length of output: 2520

Comment on lines +136 to +140
{humanFriendlyNumber(rowsRead || 0, 0)}{' '}
{estimatedRows && estimatedRows >= rowsRead
? `/ ${humanFriendlyNumber(estimatedRows)} `
: null}{' '}
rows
Copy link

Choose a reason for hiding this comment

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

Review the display logic for estimatedRows to ensure clarity and accuracy.

Consider adding a label or tooltip to clarify what "estimated rows" means to the user, especially if the actual number of rows can significantly differ from the estimate.

Copy link
Contributor

Size Change: +240 B (+0.02%)

Total Size: 1.05 MB

ℹ️ View Unchanged
Filename Size Change
frontend/dist/toolbar.js 1.05 MB +240 B (+0.02%)

compressed-size-action

@aspicer aspicer closed this May 21, 2024
@aspicer aspicer deleted the aspicer/estimated_rows branch May 21, 2024 14:48
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.

None yet

1 participant