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

Bump slinky sidecar, re-enabled volatile market #1345

Merged
merged 1 commit into from
Apr 7, 2024

Conversation

Eric-Warehime
Copy link
Contributor

Changelist

Bumps slinky sidecar to use v0.3.2 docker image which allows us to re-enable the volatile market.

Will need to be updated in dev deployments. I don't have access to that.

Test Plan

Ran localnet and got prices for TEST/USD.

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.

Copy link
Contributor

coderabbitai bot commented Apr 5, 2024

Walkthrough

The recent updates involve the uncommenting of the update_genesis_use_test_volatile_market function call across various shell scripts related to different testing environments (dev, local, and staging). This change enables the execution of this function, aiming to update the genesis configuration to incorporate test volatile markets across these environments.

Changes

File Path Change Summary
.../testnet-dev/dev.sh Uncommented update_genesis_use_test_volatile_market
.../testnet-local/local.sh Uncommented update_genesis_use_test_volatile_market
.../testnet-staging/staging.sh Uncommented update_genesis_use_test_volatile_market

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>.
    • 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/coderabbit-overrides.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
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

Actionable comments outside the diff hunks (3)
protocol/testing/testnet-local/local.sh (1)

Line range hint 110-116: Wrap variables in double quotes to prevent globbing and word splitting.

- echo "${MNEMONICS[$i]}" | dydxprotocold keys add "${MONIKERS[$i]}" --recover --keyring-backend=test --home "$VAL_HOME_DIR"
+ echo "${MNEMONICS[$i]}" | dydxprotocold keys add "${MONIKERS[$i]}" --recover --keyring-backend=test --home "$VAL_HOME_DIR"
protocol/testing/testnet-dev/dev.sh (1)

Line range hint 142-148: Wrap variables in double quotes to prevent globbing and word splitting.

- echo "${MNEMONICS[$i]}" | dydxprotocold keys add "${MONIKERS[$i]}" --recover --keyring-backend=test --home "$VAL_HOME_DIR"
+ echo "${MNEMONICS[$i]}" | dydxprotocold keys add "${MONIKERS[$i]}" --recover --keyring-backend=test --home "$VAL_HOME_DIR"
protocol/testing/testnet-staging/staging.sh (1)

Line range hint 196-202: Wrap variables in double quotes to prevent globbing and word splitting.

- echo "${MNEMONICS[$i]}" | dydxprotocold keys add "${MONIKERS[$i]}" --recover --keyring-backend=test --home "$VAL_HOME_DIR"
+ echo "${MNEMONICS[$i]}" | dydxprotocold keys add "${MONIKERS[$i]}" --recover --keyring-backend=test --home "$VAL_HOME_DIR"
Review Status

Configuration used: CodeRabbit UI

Commits Files that changed from the base of the PR and between c995787 and 1681a51.
Files ignored due to path filters (1)
  • protocol/docker-compose.yml is excluded by !**/*.yml
Files selected for processing (3)
  • protocol/testing/testnet-dev/dev.sh (1 hunks)
  • protocol/testing/testnet-local/local.sh (1 hunks)
  • protocol/testing/testnet-staging/staging.sh (1 hunks)
Additional Context Used
Path-based Instructions (3)
protocol/testing/testnet-local/local.sh (1)

Pattern **/**: Do not include a walkthrough. For all comments on line changes that are longer than 15 lines, add a prefix to the comment of what lines you are commenting on (for example: "The changes from lines 100 to 200...". Add your comment to be on the last 15 lines of the chunk rather than adding your comment to the entire chunk.

protocol/testing/testnet-dev/dev.sh (1)

Pattern **/**: Do not include a walkthrough. For all comments on line changes that are longer than 15 lines, add a prefix to the comment of what lines you are commenting on (for example: "The changes from lines 100 to 200...". Add your comment to be on the last 15 lines of the chunk rather than adding your comment to the entire chunk.

protocol/testing/testnet-staging/staging.sh (1)

Pattern **/**: Do not include a walkthrough. For all comments on line changes that are longer than 15 lines, add a prefix to the comment of what lines you are commenting on (for example: "The changes from lines 100 to 200...". Add your comment to be on the last 15 lines of the chunk rather than adding your comment to the entire chunk.

Additional comments not posted (6)
protocol/testing/testnet-local/local.sh (2)

104-104: Ensure the update_genesis_use_test_volatile_market function call is properly tested in the local environment.


Line range hint 7-7: Ensure that ./genesis.sh is correctly sourced and accessible from the script's execution context.

protocol/testing/testnet-dev/dev.sh (2)

138-138: Ensure the update_genesis_use_test_volatile_market function call is properly tested in the dev environment.


Line range hint 6-6: Ensure that ./genesis.sh is correctly sourced and accessible from the script's execution context.

protocol/testing/testnet-staging/staging.sh (2)

192-192: Ensure the update_genesis_use_test_volatile_market function call is properly tested in the staging environment.


Line range hint 6-6: Ensure that ./genesis.sh is correctly sourced and accessible from the script's execution context.

@Christopher-Li Christopher-Li merged commit 0128629 into dydxprotocol:main Apr 7, 2024
17 checks passed
@Christopher-Li
Copy link
Contributor

https://github.com/Mergifyio backport release/protocol/v5.x

Copy link
Contributor

mergify bot commented Apr 8, 2024

backport release/protocol/v5.x

✅ Backports have been created

mergify bot pushed a commit that referenced this pull request Apr 8, 2024
Christopher-Li pushed a commit that referenced this pull request Apr 9, 2024
(cherry picked from commit 0128629)

Co-authored-by: Eric Warehime <eric.warehime@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

Successfully merging this pull request may close these issues.

2 participants