Fix for the BTC oracle update and cargo update

[zmanian]

Summary by CodeRabbit

• New Features
  • Expanded the catalogue system to include two additional entries for CELLAR_RYBTC, enhancing data organization.
  • Streamlined the existing catalogue by removing outdated entries, improving overall efficiency.

[coderabbitai]

Walkthrough

The changes involve modifications to two constants in the src/cellars.rs file that define allowed positions for catalogues. The ALLOWED_V2_2_CATALOGUE_POSITIONS constant has been expanded from 22 to 24 entries, adding two new entries for CELLAR_RYBTC. In contrast, the ALLOWED_V2_5_CATALOGUE_POSITIONS constant has been reduced from 8 to 6 entries, removing the CELLAR_RYBTC entries.

Changes

File	Change Summary
src/cellars.rs	ALLOWED_V2_2_CATALOGUE_POSITIONS increased from 22 to 24 entries; ALLOWED_V2_5_CATALOGUE_POSITIONS decreased from 8 to 6 entries.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b0decf4 and d17b07c.

Files ignored due to path filters (2)

• Cargo.lock is excluded by !**/*.lock, !**/*.lock
• Cargo.toml is excluded by !**/*.toml

Files selected for processing (1)

• src/cellars.rs (2 hunks)

Additional comments not posted (2)

src/cellars.rs (2)

Line range hint 146-170: Review of Expanded Catalogue Positions

The expansion of ALLOWED_V2_2_CATALOGUE_POSITIONS to include new entries for CELLAR_RYBTC at positions 224 and 225 is noted. Ensure that these additions are consistent with the system's requirements for CELLAR_RYBTC.

Run the following script to verify the usage of CELLAR_RYBTC in the system:

Verification successful

---

Consistent Usage of CELLAR_RYBTC Verified

The CELLAR_RYBTC constant is used consistently across the src/cellars.rs file, including in catalogue positions and validation functions. No issues were found with its integration into the system.

• CELLAR_RYBTC is defined and used similarly to other cellar constants.
• It is included in the ALLOWED_V2_2_CATALOGUE_POSITIONS and other relevant contexts.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the usage of `CELLAR_RYBTC` in the system.

# Test: Search for the usage of `CELLAR_RYBTC`. Expect: Consistent usage across the system.
rg --type rust -A 5 $'CELLAR_RYBTC'

Length of output: 1889

---

172-172: Review of Reduced Catalogue Positions

The reduction of ALLOWED_V2_5_CATALOGUE_POSITIONS by removing entries for CELLAR_RYBTC at positions 224 and 225 is noted. Ensure that this removal does not impact any existing functionalities that depend on these positions.

Run the following script to verify the impact of removing CELLAR_RYBTC entries:

---

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:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• 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.
  • @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 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.