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: cursor pagination #537

Open
wants to merge 1 commit into
base: dev
Choose a base branch
from
Open

feat: cursor pagination #537

wants to merge 1 commit into from

Conversation

danidomi
Copy link
Contributor

@danidomi danidomi commented Feb 3, 2025

Summary by CodeRabbit

  • Chores
    • Adjusted the branch reference used for fetching protocol definitions, aligning with recent enhancements.

Copy link

coderabbitai bot commented Feb 3, 2025

Walkthrough

The change updates the branch variable in the proto generation script. Specifically, the injective_indexer_branch in proto/indexer/gen.sh has been changed from dev to f/add-explorer-txs-v2-messages-logs, redirecting the source of proto definitions to a new branch. No other modifications or logic changes were introduced.

Changes

File(s) Change Summary
proto/indexer/gen.sh Updated the injective_indexer_branch variable from dev to f/add-explorer-txs-v2-messages-logs.

Poem

I'm a hopping rabbit with code so neat,
Leaping from "dev" to a branch that's sweet.
My whiskers twitch for this refined change cue,
A playful update in our script's debut!
With every line, I cheer, "Hooray for code anew!" 🐇✨


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

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 27c7c7c and 99ecaae.

📒 Files selected for processing (1)
  • proto/indexer/gen.sh (1 hunks)

@@ -3,7 +3,7 @@ BUILD_DIR=$ROOT_DIR/gen
PROTO_DIR=$ROOT_DIR/proto
TS_OUTPUT_DIR=$ROOT_DIR/proto-ts
TS_STUB_DIR=$ROOT_DIR/stub
injective_indexer_branch=dev
injective_indexer_branch=f/add-explorer-txs-v2-messages-logs
Copy link

Choose a reason for hiding this comment

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

💡 Codebase verification

Action Required: Update Branch Variable Quoting

The shell script still sets the branch variable unquoted and uses it unquoted in the git clone command. To prevent potential word splitting or globbing issues—especially given that the branch name contains a slash—the variable should be quoted both at assignment and during usage. For example:

  • Change
    injective_indexer_branch=f/add-explorer-txs-v2-messages-logs
    to
    injective_indexer_branch="f/add-explorer-txs-v2-messages-logs"

  • Update the git clone command to use quotes:
    git clone https://github.com/InjectiveLabs/injective-indexer.git $BUILD_DIR -b "$injective_indexer_branch" --depth 1 --single-branch > /dev/null

Please confirm that the specified branch exists on the remote repository and contains the expected proto definitions.

🔗 Analysis chain

Updated Branch Variable & Quoting Suggestions

The branch variable injective_indexer_branch has been updated to f/add-explorer-txs-v2-messages-logs. Please confirm that this branch exists on the remote repository and contains the expected proto definitions needed for the new features (e.g., cursor pagination).

Additionally, for robustness in shell parsing—especially since the branch name includes a slash—it’s a good idea to quote the assignment and its later usage. For example, you could update the code as follows:

-injective_indexer_branch=f/add-explorer-txs-v2-messages-logs
+injective_indexer_branch="f/add-explorer-txs-v2-messages-logs"

And ensure that the branch variable is used safely in the git clone command (line 27):

- -b $injective_indexer_branch
+ -b "$injective_indexer_branch"

This will help prevent any issues related to word splitting or unintentional globbing.


I'll start by gathering more context on the file by showing its full contents to verify the branch variable assignment and its usage. This will help confirm whether the variable is used with proper quoting in the git clone command and elsewhere.

🏁 Scripts executed

The following scripts were executed for the analysis:

Error: No shell scripts found


Script:

#!/bin/bash
echo "Contents of proto/indexer/gen.sh:"
cat proto/indexer/gen.sh

Length of output: 3848

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.

1 participant