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

add endpoints for mocha, from CrypTech team #1616

Merged
merged 1 commit into from
Jun 18, 2024

Conversation

dvjromashkin
Copy link
Contributor

@dvjromashkin dvjromashkin commented Jun 18, 2024

  • New Features
    • Introduced new endpoints for Celestia testnet, including consensus, RPC, API, and gRPC services based on Archive FullNode without Pruning.
    • Added a backup explorer endpoint for easier access to testnet data.

Summary by CodeRabbit

  • New Features
    • Added new gRPC endpoints, API endpoints, and explorer endpoints for the Celestia Mocha testnet.
    • Updated URLs for accessing these new endpoints.

Archiv Fullnode, RPC, API, gRPC, Explorer
Copy link
Contributor

coderabbitai bot commented Jun 18, 2024

Walkthrough

The document nodes/mocha-testnet.md has been updated to include new gRPC, API, and explorer endpoints for the Celestia testnet. These additions help users interact with and explore the Mocha testnet more effectively by providing updated resources.

Changes

File Change Summary
nodes/mocha-testnet.md Added new endpoints for Celestia testnet, including gRPC, API, and explorer endpoints. The specific URLs and connection points are documented for easy access.

Poem

A testnet named Mocha, with endpoints so fresh,
For gRPC and APIs, to explore every mesh.
Celestia shines in the testnet sky,
Enhancing our paths as devices comply.
With URLs vast, the network will soar,
Boundless horizons forevermore. 🚀


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 63461aa and 64df6c4.

Files selected for processing (1)
  • nodes/mocha-testnet.md (5 hunks)
Additional context used
LanguageTool
nodes/mocha-testnet.md

[uncategorized] ~14-~14: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...rabica devnet](./arabica-devnet.md) for that as it is designed for development purpo...


[style] ~75-~75: Consider a shorter alternative to avoid wordiness. (IN_ORDER_TO_PREMIUM)
Context: ...nsensus node](./full-consensus-node.md) in order to download full blocks from it. ::: - `p...

Markdownlint
nodes/mocha-testnet.md

132-132: null (MD039, no-space-in-links)
Spaces inside link text

Additional comments not posted (5)
nodes/mocha-testnet.md (5)

87-88: Ensure the new RPC and gRPC endpoints are correctly documented and accessible.


112-112: Verify the accessibility and correctness of the RPC endpoint.


137-137: Confirm the API endpoint is functional and correctly documented.


224-224: Confirm the explorer endpoint is functional and correctly linked.

Verification successful

The explorer endpoint is functional, as indicated by the HTTP/1.1 200 OK response status.

  • The link is correctly included in the documentation at line 224 of the nodes/mocha-testnet.md file.
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify the functionality of the explorer endpoint.

# Test: Check if the explorer link is functional.
curl -I https://explorers.cryptech.com.ua/Celestia-Testnet

Length of output: 879


165-165: Ensure the gRPC endpoint is correctly configured and accessible.

@jcstein jcstein merged commit 1fd22f5 into celestiaorg:main Jun 18, 2024
1 check passed
Copy link

gitpoap-bot bot commented Jun 18, 2024

Congrats, your important contribution to this open-source project has earned you a GitPOAP!

GitPOAP: 2024 Celestia Contributor:

GitPOAP: 2024 Celestia Contributor GitPOAP Badge

Head to gitpoap.io & connect your GitHub account to mint!

Learn more about GitPOAPs here.

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