b_t5-execution_chain: Ethereum 1.0 / Legacy Chain Associated Methods and Data Models #43
Conversation
| echo "install sqlx... " | ||
| GETH_URL: "ws://localhost:8546" # Set local setup Geth Endpoint | ||
| run: | | ||
| echo "Install dependencies for Geth on local" |
There was a problem hiding this comment.
As the Ethereum analysis project grows, its codebase, test cases, and CI/CD pipeline execution logic are becoming increasingly complex. To mitigate this complexity, it would be beneficial to extract the project into an independent repository. This separation will help prevent new commits from causing test failures that block the entire CI/CD pipeline.
Furthermore, CI/CD commands should be executed in isolated jobs rather than combining them into a single sequence of shell commands within a ‘run’ step. This approach improves job parallelism and maintainability. It’s also important to note that tutorials 1, 2, 3, 4, and 5 are largely independent of each other, so they can be executed in parallel without interdependencies.
…ruct object, then append all coming real time items into stream
…ponse and add codes for create different kind of request which to be sent to ethereum node in websocket
In this commit, we focus on the execution chain(Ethereum 1.0 Chain) associated with data fetching functions, data model encapsulations, and Geth usages.
What's more, we added a multi-thread-based event-driven message handle logic to this commit.