Update localnet sidecar to 1.0.10

[chenyaoy]

Changelist

[Describe or list the changes made in this PR]

Test Plan

[Describe how this PR was tested (if applicable)]

Author/Reviewer Checklist

• If this PR has changes that result in a different app state given the same prior state and transaction list, manually add the state-breaking label.
• If the PR has breaking postgres changes to the indexer add the indexer-postgres-breaking label.
• If this PR isn't state-breaking but has changes that modify behavior in PrepareProposal or ProcessProposal, manually add the label proposal-breaking.
• If this PR is one of many that implement a specific feature, manually label them all feature:[feature-name].
• If you wish to for mergify-bot to automatically create a PR to backport your change to a release branch, manually add the label backport/[branch-name].
• Manually add any of the following labels: refactor, chore, bug.

Summary by CodeRabbit

• New Features

  • Removed the "polymarket_api" configuration, signaling a shift in market data handling.
  • Upgraded the slinky-sidecar service to a newer version, potentially enhancing performance and bug fixes.

• Bug Fixes

  • Updated Docker image may resolve existing issues related to the previous version.

[coderabbitai]

Walkthrough

The recent updates involve significant changes to the configuration files, including the removal of the "polymarket_api" section from a JSON file, indicating a transition away from this data source. Additionally, the Docker configuration has been updated to use a newer version of the slinky-sidecar image. These modifications suggest an evolution in how market data is managed and a commitment to utilizing improved service versions.

Changes

Files	Change Summary
protocol/contrib/slinky/oracle.json	Removed the entire "polymarket_api" configuration block, impacting how market data will be handled within the system.
protocol/docker-compose.yml	Updated the Docker image for the slinky0 service from version v1.0.8 to v1.0.10, indicating enhancements while preserving existing entrypoint and environment settings.

Poem

🐰 In fields where data dances bright,
The polymarket took its flight.
With Slinky’s sidecar freshly dressed,
We leap towards a brand new quest!
New paths we chart, with hops of cheer,
A future clear, the time is here! 🌟

---

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

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9263b4c and b7893ac.

Files selected for processing (2)

• protocol/contrib/slinky/oracle.json (1 hunks)
• protocol/docker-compose.yml (1 hunks)

Files skipped from review due to trivial changes (1)

• protocol/docker-compose.yml

Additional comments not posted (1)

protocol/contrib/slinky/oracle.json (1)

Line range hint 1-22: Verify the impact of removing "polymarket_api".

The removal of the "polymarket_api" configuration block indicates a significant change in data sourcing. Ensure that this does not disrupt any functionalities or components that depended on this API. Verify that the application can still access necessary market data without this configuration.

Run the following script to search for any references to "polymarket_api" in the codebase, which might indicate dependencies or usage that need to be addressed:

Verification successful

---

No impact from the removal of "polymarket_api".

The search across the codebase did not find any references to "polymarket_api", indicating that its removal from the configuration does not affect other components or functionalities. The application should continue to function correctly without it.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify if "polymarket_api" is referenced elsewhere in the codebase.

# Test: Search for references to "polymarket_api". Expect: No references found.
rg --type json --type py --type js --type ts 'polymarket_api'

Length of output: 61