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

Ci/fix peers #753

Merged
merged 3 commits into from
May 28, 2024
Merged

Ci/fix peers #753

merged 3 commits into from
May 28, 2024

Conversation

ccamel
Copy link
Member

@ccamel ccamel commented May 27, 2024

Reactivates peers retrieval and update job for the drunemeton-1 network. It may not be absolutely essential, but it aims to be helpful, I guess.

@ccamel ccamel self-assigned this May 27, 2024
Copy link

coderabbitai bot commented May 27, 2024

Walkthrough

The changes encompass updates to the GitHub workflow and peer addresses for the drunemeton-1 chain. The workflow modifications include scheduling, error handling, and formatting improvements. The peer list has been revised with new IP addresses and port numbers, enhancing network connectivity and reliability.

Changes

File Path Change Summary
.github/workflows/update-peers.yml Enabled schedule, updated target node and chain info, improved listen address parsing, added error handling, and enhanced formatting.
chains/drunemeton-1/peers.txt Updated peer addresses and added new peer entries for better network connectivity.

Sequence Diagram(s) (Beta)

The changes do not introduce a new feature or significantly alter the control flow, so a sequence diagram is not provided.


Tip

Early Access Features
  • gpt-4o model for chat

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to full the 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 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.

@ccamel ccamel marked this pull request as ready for review May 27, 2024 16:30
Copy link

@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

Outside diff range and nitpick comments (1)
.github/workflows/update-peers.yml (1)

Line range hint 43-91: Enhanced peer retrieval logic with robust parsing and error handling.

The peer retrieval script has been significantly improved. Consider encapsulating the peer address parsing logic into a separate function or module for better maintainability and potential reuse.

+ def parse_peer_address(peer):
+     peerId = peer['node_info']['id']
+     remoteIp = peer['remote_ip']
+     listen_address = peer['node_info']['listen_addr']
+     match = re.match(r"(?:.+:\/\/)?(?:.+):(\d+)", listen_address)
+     if match:
+         listen_port = match.group(1)
+     else:
+         raise ValueError("Invalid listen address: {}".format(listen_address))
+
+     match ip_class(remoteIp):
+         case IPClass.IPv4:
+             return f"{peerId}@{remoteIp}:{listen_port}"
+         case IPClass.IPv6:
+             return f"{peerId}[@{remoteIp}]:{listen_port}"
+         case _:
+             raise ValueError("Invalid IP address: {}".format(remoteIp))
+
+ return parse_peer_address(peer)

This refactor suggestion aims to improve the readability and maintainability of the code by separating concerns.

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between a71a1a0 and 1c84fa0.
Files selected for processing (1)
  • .github/workflows/update-peers.yml (4 hunks)
Additional comments not posted (2)
.github/workflows/update-peers.yml (2)

6-7: Scheduled run added for Mondays.

This ensures the peer list is regularly updated, which is crucial for maintaining network connectivity.


19-20: Updated node and chain information.

This change targets the drunemeton-1 network specifically, aligning with the PR's objectives to reactivate peer retrieval for this network.

@ccamel ccamel requested a review from amimart May 27, 2024 16:38
Copy link

@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 1c84fa0 and b1c840c.
Files selected for processing (1)
  • chains/drunemeton-1/peers.txt (1 hunks)
Additional comments not posted (6)
chains/drunemeton-1/peers.txt (6)

1-1: Updated peer address appears correctly formatted.


2-2: New peer address added and correctly formatted.


3-3: New peer address added and correctly formatted.


4-4: New peer address added and correctly formatted.


8-8: Updated peer address appears correctly formatted.


9-9: New peer address added and correctly formatted.

@ccamel ccamel merged commit 3841959 into main May 28, 2024
10 checks passed
@ccamel ccamel deleted the ci/fix-peers branch May 28, 2024 08:24
@coderabbitai coderabbitai bot mentioned this pull request Sep 9, 2024
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.

3 participants