mirror/erigon-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/erigon-pulse.git synced 2025-01-03 09:37:38 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update README.md (#9112)

Browse Source 
Hi, I made three suggestions for this section:

- "devenet" should be "devnet" (typo).

- "are currently build" should be "are currently built" (grammatical
error).

- "sptep" should be "step" (typo).

Thanks.
This commit is contained in:
umba 2024-01-03 15:01:40 +03:00 committed by GitHub
parent a2274f36e5
commit a645ef62a7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
cmd/devnet/README.md
View File

@ -9,7 +9,7 @@ The devnet code performs 3 main functions:
* It allows for the specification of a series of scenarios which will be run against the nodes on that internal network * It allows for the specification of a series of scenarios which will be run against the nodes on that internal network
* It can optionally run a `support` connection which allows the nodes on the network to be connected to the Erigon diagnostic system * It can optionally run a `support` connection which allows the nodes on the network to be connected to the Erigon diagnostic system
The specification of both nodes and scenarios for the devenet is done by specifying configuration objects. These objects are currently build in code using go `structs` but are capable of being read as configuration. The specification of both nodes and scenarios for the devnet is done by specifying configuration objects. These objects are currently built in code using go `structs` but are capable of being read as configuration.
## Devnet runtime start-up ## Devnet runtime start-up
@ -85,7 +85,7 @@ func init() {
) )
} }
``` ```
Each step method will be called with a `context.Context` as its initial argument. This context provides access to the underlying devnet - so the sptep handler can use it for processing. Each step method will be called with a `context.Context` as its initial argument. This context provides access to the underlying devnet - so the step handler can use it for processing.
```go ```go
func PingErigonRpc(ctx context.Context) error { func PingErigonRpc(ctx context.Context) error {