Refactor to single file

[faddat]

The app got too complex so I made it a single file. Also I made a javascript version which gets the job done quite well.

Summary by CodeRabbit

• New Features

  • Introduced a GitHub Actions workflow for testing and running Go code.
  • Added network crawling functionality to fetch information and status from URLs.
  • Enhanced the RPC crawler application to support concurrent node checking and data processing.

• Improvements

  • Updated the main function to handle multiple initial nodes and write data to a TOML file.

[coderabbitai]

Walkthrough

The recent updates introduce a GitHub Actions workflow for testing Go code, add network crawling capabilities in JavaScript, and significantly enhance the functionality of a Go-based RPC crawler application. These changes focus on improving automation, concurrency, and network data processing.

Changes

Files	Change Summary
.github/workflows/test.yml	Introduced a GitHub Actions workflow for testing Go code on multiple OS versions.
javascript/crawl.js	Added functions for network crawling, fetching network information, and recursively crawling peers.
main.go	Refactored global variables, added concurrency with goroutines, and introduced multiple new functions for node checking, data processing, and network operations.

🐇
In the code where bytes do flow,
New tests and nodes now swiftly grow.
With Go and JavaScript in hand,
We crawl and fetch across the land.
Actions run, the network's spun,
Our work is never truly done. 🌐✨

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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/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.

[coderabbitai]

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 5c81988 and 12b441e.

Files ignored due to path filters (2)

• go.mod is excluded by !**/*.mod
• go.sum is excluded by !**/*.sum

Files selected for processing (4)

• .github/workflows/test.yml (1 hunks)
• javascript/crawl.js (1 hunks)
• main.go (1 hunks)
• nodes.toml (1 hunks)

Files not summarized due to errors (1)

• nodes.toml: Error: Message exceeds token limit

Additional comments not posted (18)

nodes.toml (1)

1-13: The updates to the node URLs in the TOML configuration are correct and align with the PR's objectives.

.github/workflows/test.yml (2)

1-17: The configuration for the test-nocache job in the GitHub Actions workflow is correctly set up to test the Go code across multiple operating systems without caching.

---

18-26: The run job in the GitHub Actions workflow is correctly configured to install and execute the Go application, ensuring the application's functionality is tested upon each push or pull request.

javascript/crawl.js (3)

6-14: The fetchNetInfo function is well-implemented with proper error handling and logging, making it robust for network operations.

---

16-24: The fetchStatus function correctly implements error handling and logging, ensuring reliable status fetching from network URLs.

---

26-69: The crawlNetwork function is correctly implemented for recursive network crawling with appropriate base case handling and error management.

main.go (12)

37-60: The main function is well-structured, correctly handling multiple initial nodes with goroutines and ensuring data consistency with proper synchronization.

---

62-206: The CheckNode function is robust, with comprehensive error handling, concurrency management, and network operations, aligning well with the application's requirements.

---

208-214: The FetchClient function is correctly implemented to establish an HTTP client with a specified timeout, enhancing network communication reliability.

---

216-223: The BuildRPCAddress function effectively handles different IP scenarios to construct accurate RPC addresses, crucial for network operations.

---

225-261: The WriteSectionToToml function is implemented with error handling to ensure reliable writing of node information to the TOML file.

---

263-291: The ProcessPeer function correctly handles peer processing and node checking on common RPC ports, effectively managing concurrency with goroutines.

---

293-297: The FetchNetInfo function is well-implemented for fetching network information, with proper error handling to ensure robustness.

---

299-303: The NormalizeAddressWithRemoteIP function effectively replaces local IP placeholders with the actual remote IP, ensuring accurate network addresses.

---

305-310: The IsNodeVisited function correctly uses read locks to ensure thread safety while checking if a node has been visited.

---

312-316: The MarkNodeAsVisited function is correctly implemented with locks to ensure thread safety while marking a node as visited.

---

318-336: The WriteNodesToToml function is well-implemented, handling file creation and write operations with appropriate error handling, ensuring data integrity.

---

338-354: The WriteSectionToTomlSlice function effectively writes sections to a TOML file from a slice of nodes, with error handling to ensure data integrity.