Skip to content

Conversation

gfyrag
Copy link
Contributor

@gfyrag gfyrag commented Aug 13, 2025

No description provided.

@gfyrag gfyrag requested a review from a team as a code owner August 13, 2025 10:34
Copy link

coderabbitai bot commented Aug 13, 2025

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (1)
  • main

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/v2.1-hacked-version

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

Comment on lines +293 to +295
[]bunpaginate.PaginationColumnOption{
bunpaginate.WithNullsOrder(bunpaginate.NullsOrderLast),
},
Copy link

Choose a reason for hiding this comment

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

I know that setting NULLS LAST can affect the query plan but not being super familiar with ledger it's not particularly easy for me to grasp what kind of effect this will have.

Are we rolling this out to all customers? If it's temporary when do we roll it back?

Since the team spent the last week attempting to field customer questions about ledger performance and we struggled due to a lack of paper trail of the previous benchmarks and whatnot that had been done, I was thinking perhaps it would be nice if when you create PRs like this you could add some context?

I don't really care how it's done, but it's rough to follow these empty PR descriptions. Here are some ideas that might help remove some of the "black box" aspect of ledger:

  • link to a related linear ticket or the Pylon thread with the customer conversation
  • show the before/after EXPLAIN statements as part of the PR description
  • just describe what kind of impact you expect the change to have in a few words

@gfyrag gfyrag force-pushed the chore/v2.1-hacked-version branch from c08b711 to 394973a Compare August 13, 2025 11:46
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.

2 participants