Skip to content

Add Solana account limits#71

Merged
akegaviar merged 2 commits intomainfrom
fix/solana-limits
May 30, 2025
Merged

Add Solana account limits#71
akegaviar merged 2 commits intomainfrom
fix/solana-limits

Conversation

@akegaviar
Copy link
Copy Markdown
Member

@akegaviar akegaviar commented May 30, 2025

Summary by CodeRabbit

  • Documentation
    • Added information about Solana accounts excluded from indexing and streaming, specifying the public keys that are unavailable for querying or streaming.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 30, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

Two documentation files were updated to specify that two particular Solana accounts are excluded from querying and streaming. These accounts are now explicitly listed in the relevant sections of the documentation, clarifying their unavailability for both indexing and streaming through the system.

Changes

File(s) Change Summary
docs/limits.mdx Added a section listing two Solana accounts excluded from indexing.
docs/yellowstone-grpc-geyser-plugin.mdx Updated "Limits" section to note that the same two Solana accounts are unavailable for streaming.

Possibly related PRs

  • Add Solana account limits #71: Adds the same documentation sections specifying Solana accounts excluded from indexing and streaming, directly related to this update.
  • Add Geyser limits #46: Adds general usage limits and pricing tiers for the Yellowstone gRPC Geyser plugin, related by topic but without overlapping specific excluded accounts.

Poem

Two Solana accounts, now off the map,
Not for streaming, nor for query’s tap.
The docs have been sharpened with clarity’s pen,
So users and rabbits know what, where, and when.
With paws on the keyboard, I hop and I cheer—
Documentation is crystal, the limits are clear!
🐇✨


📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 94a883a and 8688870.

📒 Files selected for processing (2)
  • docs/limits.mdx (1 hunks)
  • docs/yellowstone-grpc-geyser-plugin.mdx (1 hunks)

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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

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

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

Copy link
Copy Markdown
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

🧹 Nitpick comments (2)
docs/limits.mdx (1)

137-143: Refine section phrasing and consistency

To improve clarity and match the style in docs/yellowstone-grpc-geyser-plugin.mdx, update the sentence to include “are” and mirror the “excluded” terminology. For example:

## Solana accounts excluded from indexing
- The following Solana accounts unavailable for querying:
+ The following Solana accounts are excluded from querying:
docs/yellowstone-grpc-geyser-plugin.mdx (1)

51-55: Promote exclusion notice to a heading and unify terminology

This note is valuable but would benefit from being a distinct subheading under “Limits” and using the same “excluded” phrasing. For example:

- The following Solana accounts unavailable for streaming:
+ ### Solana accounts excluded from streaming
+ The following Solana accounts are excluded from streaming:
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 163a996 and 94a883a.

📒 Files selected for processing (2)
  • docs/limits.mdx (1 hunks)
  • docs/yellowstone-grpc-geyser-plugin.mdx (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Mintlify Deployment

@akegaviar akegaviar merged commit 6910442 into main May 30, 2025
3 of 4 checks passed
@akegaviar akegaviar deleted the fix/solana-limits branch July 2, 2025 00:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant