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

feat(testnet): enable osmosis grpc #128

Merged
merged 3 commits into from
Jun 18, 2024
Merged

Conversation

manu0466
Copy link
Contributor

Overview

This PR updates the local-osmosis-testnet-continue.sh script to start the Osmosis node with the gRPC endpoint enabled.

closes: #XXXX

What changes have been made in this PR?

  • [ ]

Checklist


  • Appropriate labels applied
  • Targeted PR against correct branch
  • Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
  • Wrote unit and integration
  • Updated relevant documentation

@manu0466 manu0466 requested a review from jaybxyz as a code owner June 18, 2024 12:30
Copy link
Contributor

coderabbitai bot commented Jun 18, 2024

Walkthrough

The changes encompass renaming and reorganizing scripts for consistency across the testnet setup. Specifically, they update script names related to initializing stake contracts and augment the tmux session command for stability in an Osmosis testnet. The modifications enhance clarity and functionality within the scripts and Makefile.

Changes

File Change Summary
scripts/testnet/Local-Testnet.md Updated script name from init_stake_contract.sh to init-stake-contract.sh.
scripts/testnet/local-osmosis-testnet-continue.sh Added --grpc.enable flag and --grpc.address 0.0.0.0:9090 option for osmosis1 tmux session.
Makefile Renamed and reorganized script calls for stake contract initialization and migration. Updated filenames.

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

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: 1

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4329aa6 and 3ea4519.

Files selected for processing (2)
  • scripts/testnet/Local-Testnet.md (1 hunks)
  • scripts/testnet/local-osmosis-testnet-continue.sh (1 hunks)
Additional context used
LanguageTool
scripts/testnet/Local-Testnet.md

[uncategorized] ~19-~19: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...1lh0u9sug6qh922gjpal3frwtacaums4s7lkyl9`: Osmosis trader account used to swap the...


[uncategorized] ~20-~20: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...1sfhy3emrgp26wnzuu64p06kpkxd9phel74e0yx`: Celestia account that stakes the TIA on...


[uncategorized] ~21-~21: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...1lh0u9sug6qh922gjpal3frwtacaums4s8w5yn6`: Celestia account that operates the stak...


[uncategorized] ~22-~22: Loose punctuation mark. (UNLIKELY_OPENING_PUNCTUATION)
Context: ...12rzczckgh8fqq533t0xqhqrrzdk76du3dxrx9q`: Celestia account where the staking rewa...


[uncategorized] ~110-~110: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE_2)
Context: .... - This enables Tx indexing in Celestia so tooling can confirm transactions done o...


[duplication] ~114-~114: Possible typo: you repeated a word (ENGLISH_WORD_REPEAT_RULE)
Context: ... the relayer on Celestia side and store in in a file celestia-relayer-key.json ``` c...


[duplication] ~120-~120: Possible typo: you repeated a word (ENGLISH_WORD_REPEAT_RULE)
Context: ...r the relayer on Osmosis side and store in in a file osmosis-relayer-key.json ``` os...


[uncategorized] ~157-~157: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...er --b-port transfer Start Hermes (subsequently you only need to run this command) ...


[grammar] ~165-~165: It seems that a verb or a comma is missing. (MD_DT_JJ)
Context: ...rt ``` ### Check Validator output You can the output of the validators with Tmux ...

Markdownlint
scripts/testnet/Local-Testnet.md

59-59: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


18-18: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


7-7: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


13-13: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


66-66: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


76-76: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


102-102: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


116-116: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


122-122: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


128-128: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


135-135: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


143-143: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


150-150: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


159-159: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


167-167: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified


179-179: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified

Additional comments not posted (1)
scripts/testnet/local-osmosis-testnet-continue.sh (1)

13-16: The addition of gRPC configuration options in the startup command enhances functionality as intended.

Ensure that all dependent scripts and configurations are updated to handle these new gRPC settings correctly.

@@ -38,7 +38,7 @@ Before deploying the contracts, you need to:
After completing the above steps, you can deploy the contracts by running:

```sh
./init_stake_contract.sh
./init-stake-contract.sh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tip

Codebase Verification

The old script name init_stake_contract.sh is still referenced in the Makefile. This needs to be updated to the new script name init-stake-contract.sh.

  • Makefile: bash scripts/testnet/init_stake_contract.sh
Analysis chain

The script name change from init_stake_contract.sh to init-stake-contract.sh improves consistency with naming conventions.

Ensure all documentation and references to this script across the project are updated to reflect this change.

Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify all references to the old script name are updated.

# Search for the old script name in the entire project. Expect: No occurrences of the old script name.
rg --type md 'init_stake_contract.sh'

Length of output: 37



Script:

#!/bin/bash
# Description: Verify all references to the old script name are updated in the entire project, including non-markdown files.

# Search for the old script name in the entire project. Expect: No occurrences of the old script name.
rg 'init_stake_contract.sh'

Length of output: 81

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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 3ea4519 and 74246f9.

Files selected for processing (1)
  • Makefile (1 hunks)
Files skipped from review due to trivial changes (1)
  • Makefile

@RiccardoM RiccardoM merged commit bd2d7d2 into main Jun 18, 2024
1 check passed
@RiccardoM RiccardoM deleted the manuel/enable-osmosis-grpc branch June 18, 2024 13:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants