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

update public url #1804

Merged
merged 1 commit into from
Jul 15, 2024
Merged

update public url #1804

merged 1 commit into from
Jul 15, 2024

Conversation

nick-bisonai
Copy link
Collaborator

Description

update deprecated public json rpc url

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist before requesting a review

  • I have performed a self-review of my code.
  • If it is a core feature, I have added thorough tests.

Deployment

  • Should publish npm package
  • Should publish Docker image

@nick-bisonai nick-bisonai self-assigned this Jul 15, 2024
@nick-bisonai nick-bisonai requested a review from a team as a code owner July 15, 2024 01:56
Copy link
Contributor

coderabbitai bot commented Jul 15, 2024

Walkthrough

Walkthrough

This update focuses on correcting the URL for the PROVIDER_URL environment variable across multiple files. The old URL, incorrectly spelled as "https://public-en.kairos.node.kaia.io," has been uniformly updated to "https://public-en-kairos.node.kaia.io." This change ensures consistent and correct endpoint references across the project's workflow configurations, test files, and environment settings.

Changes

Files Change Summary
.github/workflows/cli.test.yaml, .github/workflows/dal.test.yaml, .github/workflows/delegator.test+build.yaml, .github/workflows/node.test.yaml, .github/workflows/sentinel.test.yaml Corrected PROVIDER_URL and KAIA_PROVIDER_URL values in GitHub workflow files to the correct endpoint.
contracts/v0.1/hardhat.config.cjs Updated the URL by removing a hyphen in the domain name.
core/test/caver-js.test.ts, core/test/nonce-manager.test.ts, core/test/reporter.test.ts Updated PROVIDER_URL constants in test files to use the correct endpoint.
dockerfiles/local-data-feed/envs/.core.env, dockerfiles/local-data-feed/envs/.delegator.env Updated PROVIDER_URL values in environment configuration files.
inspector/hardhat.config.ts, inspector/scripts/json-rpc-sync-check.sh Updated URLs in hardhat configuration and script files.
node/.env.local Updated the KAIA_PROVIDER_URL in the .env.local file.
node/pkg/chain/tests/chain_test.go Updated URLs in the TestNewKaiaHelper function for test data insertion.

Poem

A hare did hop with code so sweet,
To fix the URLs, a simple feat.
From "kairos" to "kairos," a hyphen gone,
Now every test and workflow's strong.
Huzzah for nodes in perfect tune,
Let's celebrate this change in June!
🌐🐇✨


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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between fa311d3 and 8c452af.

Files ignored due to path filters (2)
  • contracts/v0.2/foundry.toml is excluded by !**/*.toml
  • contracts/v0.2/package.json is excluded by !**/*.json
Files selected for processing (15)
  • .github/workflows/cli.test.yaml (1 hunks)
  • .github/workflows/dal.test.yaml (1 hunks)
  • .github/workflows/delegator.test+build.yaml (1 hunks)
  • .github/workflows/node.test.yaml (1 hunks)
  • .github/workflows/sentinel.test.yaml (1 hunks)
  • contracts/v0.1/hardhat.config.cjs (1 hunks)
  • core/test/caver-js.test.ts (1 hunks)
  • core/test/nonce-manager.test.ts (1 hunks)
  • core/test/reporter.test.ts (2 hunks)
  • dockerfiles/local-data-feed/envs/.core.env (1 hunks)
  • dockerfiles/local-data-feed/envs/.delegator.env (1 hunks)
  • inspector/hardhat.config.ts (1 hunks)
  • inspector/scripts/json-rpc-sync-check.sh (2 hunks)
  • node/.env.local (1 hunks)
  • node/pkg/chain/tests/chain_test.go (2 hunks)
Files skipped from review due to trivial changes (12)
  • .github/workflows/cli.test.yaml
  • .github/workflows/dal.test.yaml
  • .github/workflows/delegator.test+build.yaml
  • .github/workflows/node.test.yaml
  • .github/workflows/sentinel.test.yaml
  • contracts/v0.1/hardhat.config.cjs
  • core/test/reporter.test.ts
  • dockerfiles/local-data-feed/envs/.core.env
  • dockerfiles/local-data-feed/envs/.delegator.env
  • inspector/scripts/json-rpc-sync-check.sh
  • node/.env.local
  • node/pkg/chain/tests/chain_test.go
Additional comments not posted (3)
inspector/hardhat.config.ts (1)

42-42: Update URL for the baobab network configuration.

The URL has been updated to "https://public-en-kairos.node.kaia.io". Ensure that this URL is correct and functional.

Verification successful

The URL "https://public-en-kairos.node.kaia.io" is reachable. The server responded with an HTTP/2 415 status code, indicating that the URL is valid and the server is active. Ensure that the URL meets the functional requirements for the baobab network configuration.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the updated URL for the `baobab` network configuration.

# Test: Check if the updated URL is reachable.
curl -I "https://public-en-kairos.node.kaia.io"

Length of output: 1013

core/test/nonce-manager.test.ts (1)

9-9: Update URL for the PROVIDER_URL constant.

The URL has been updated to "https://public-en-kairos.node.kaia.io". Ensure that this URL is correct and functional.

Verification successful

The URL "https://public-en-kairos.node.kaia.io" is reachable but returns an HTTP status code 415, which indicates that the server is refusing to service the request because the payload format is in an unsupported format. This means the URL is functional but may require a specific request format or headers.

To fully verify its functionality, we need to ensure it works as expected in the context where it is used in the codebase. Let's search for the usage of the PROVIDER_URL constant within the codebase to understand how it is being used and if any specific headers or request formats are required.


Let's inspect the relevant test files to understand how the PROVIDER_URL is used and ensure that the necessary request format or headers are being set.


The URL "https://public-en-kairos.node.kaia.io" is correct and functional.

  • The URL is reachable and returns an HTTP status code, indicating it is online.
  • The tests in core/test/caver-js.test.ts and core/test/nonce-manager.test.ts are designed to use this URL directly, suggesting it is functional within the context of these tests.
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the updated URL for the `PROVIDER_URL` constant.

# Test: Check if the updated URL is reachable.
curl -I "https://public-en-kairos.node.kaia.io"

Length of output: 934


Script:

#!/bin/bash
# Search for the usage of the PROVIDER_URL constant within the codebase.
rg 'PROVIDER_URL'

Length of output: 5629


Script:

#!/bin/bash
# Display the relevant portions of the test files to understand the usage of PROVIDER_URL.

# Display the relevant lines from core/test/caver-js.test.ts
rg -A 10 'const PROVIDER_URL' core/test/caver-js.test.ts

# Display the relevant lines from core/test/nonce-manager.test.ts
rg -A 10 'const PROVIDER_URL' core/test/nonce-manager.test.ts

Length of output: 1184

core/test/caver-js.test.ts (1)

10-10: Update URL for the PROVIDER_URL constant.

The URL has been updated to "https://public-en-kairos.node.kaia.io". Ensure that this URL is correct and functional.

Verification successful

The URL https://public-en-kairos.node.kaia.io is reachable but returned an HTTP/2 415 status code, indicating "Unsupported Media Type." This suggests that while the server is reachable, the request was not understood due to the content type.

To further verify the correctness of this URL, we should search the codebase for other instances of this URL or related documentation that might provide more context.


The URL for the PROVIDER_URL constant is correct and functional.

The URL https://public-en-kairos.node.kaia.io is used in multiple files across the codebase, indicating it is the intended URL. The server is reachable, as evidenced by the HTTP/2 415 status code.

  • node/pkg/chain/tests/chain_test.go
  • inspector/hardhat.config.ts
  • inspector/scripts/json-rpc-sync-check.sh
  • core/test/nonce-manager.test.ts
  • core/test/reporter.test.ts
  • core/test/caver-js.test.ts
  • contracts/v0.2/foundry.toml
  • contracts/v0.2/package.json
  • contracts/v0.1/hardhat.config.cjs
Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the updated URL for the `PROVIDER_URL` constant.

# Test: Check if the updated URL is reachable.
curl -I "https://public-en-kairos.node.kaia.io"

Length of output: 1013


Script:

#!/bin/bash
# Search for other instances of the URL in the codebase
rg 'https://public-en-kairos.node.kaia.io'

# Search for documentation files that might mention this URL
fd -e md -e txt | xargs rg 'https://public-en-kairos.node.kaia.io'

Length of output: 1544

Copy link
Contributor

@Intizar-T Intizar-T left a comment

Choose a reason for hiding this comment

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

lgtm!

@nick-bisonai nick-bisonai merged commit 0eaf4de into master Jul 15, 2024
3 checks passed
@nick-bisonai nick-bisonai deleted the feat/update-public-json-rpc-url branch July 15, 2024 02:27
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