feat: add end-key to pool

[shifty11]

Summary by CodeRabbit

• New Features

  • Added a new pool status POOL_STATUS_END_KEY_REACHED to indicate when a pool has reached its end key.
  • Enhanced the UpdatePool function to allow updating the EndKey of a pool.

• Bug Fixes

  • Implemented a check in AssertPoolCanRun to prevent a pool from running if the end key is reached.

• Documentation

  • Updated API documentation to include the new end_key property and POOL_STATUS_END_KEY_REACHED.

• Tests

  • Added tests to ensure proper handling when the end key of a pool is reached.

[coderabbitai]

Warning

Rate Limit Exceeded

@troykessler has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 23 minutes and 16 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between d7f4681 and a0802e7.

Walkthrough

This update introduces a new pool status POOL_STATUS_END_KEY_REACHED and an end_key property across various components of the system. It enhances the handling of pool operations when an end key is reached, preventing further actions and enabling status updates. This change affects API definitions, protocol buffers, and server logic, ensuring consistency and functionality in response to reaching pool end keys.

Changes

Files	Change Summary
docs/static/openapi.yml proto/kyve/pool/v1beta1/pool.proto proto/kyve/pool/v1beta1/events.proto proto/kyve/pool/v1beta1/tx.proto	Added POOL_STATUS_END_KEY_REACHED and end_key property.
x/bundles/keeper/logic_bundles.go x/bundles/keeper/logic_bundles_test.go	Added logic and tests for handling pool operations when end key is reached.
x/bundles/types/errors.go x/pool/types/msgs.go	Introduced new error ErrEndKeyReached and updated PoolUpdate struct with EndKey.
x/pool/keeper/msg_server_update_pool.go x/pool/keeper/msg_server_update_pool_test.go	Updated UpdatePool function and tests to handle EndKey.
x/query/keeper/helper.go	Added logic to determine pool status based on EndKey and CurrentKey.

🐇✨
In the code's garden, changes bloom,
END_KEY_REACHED, a new tune's croon.
When pools cease to flow,
We now rightly know,
To halt with grace, beneath the moon.
🌒🌟

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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.

[troykessler]

Please also add the "end_key" to MsgCreatePool in proto/kyve/pool/v1beta1/tx.proto and add test if property does get created correctly