status-im/nimbus-eth1
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth1.git synced 2025-02-24 17:58:30 +00:00
Code Issues Projects Releases Wiki Activity

update readme.md

Browse Source
This commit is contained in:
andri lim 2019-01-09 15:35:18 +07:00 committed by zah
parent 729686ff57
commit 8978d1fcaa
1 changed files with 25 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
premix/readme.md
View File

@ -18,15 +18,19 @@ This test case then can be integrated with nimbus project test suite.
![screenshot](assets/images/premix_screenshot.png) ![screenshot](assets/images/premix_screenshot.png)
## Requirements ## Requirements
Before you start to use premix debugging tool there are several things you need to prepare. The first one is you need to install `geth` from [source](https://github.com/ethereum/go-ethereum/releases) or [binary](https://ethereum.github.io/go-ethereum/downloads/). Then you can run it with this command: Before you start to use premix debugging tool there are several things you need to prepare.
The first one is you need to install `geth` from [source](https://github.com/ethereum/go-ethereum/releases)
or [binary](https://ethereum.github.io/go-ethereum/downloads/). Then you can run it with this command:
```bash ```bash
geth --rpc --rpcapi eth,debug --syncmode full --gcmode=archive geth --rpc --rpcapi eth,debug --syncmode full --gcmode=archive
``` ```
You need to run it until it synced past the problematic block you want to debug. After that you can stop it by pressing `CTRL-C` and rerun it with addition flags `--maxpeers 0` if you want it to stop syncing or let it run as is if you want keep syncing. You need to run it until it synced past the problematic block you want to debug.
After that you can stop it by pressing `CTRL-C` and rerun it with additional
flags `--maxpeers 0` if you want it to stop syncing or let it run as is if you want keep syncing.
The next requirement is you should build nimbus and premix with latest dependencies: The next requirement is you should build Nimbus and Premix with latest dependencies:
```bash ```bash
nim c nimbus/nimbus nim c nimbus/nimbus
@ -39,23 +43,34 @@ After you successfully build nimbus and premix, you can run nimbus with this co
nimbus --prune:archive nimbus --prune:archive
``` ```
Nimbus will try to sync up to problematic block then it will stop and execute premix. You can see the premix report page by opening `premix/index.html` if premix failed to open your default browser. Nimbus will try to sync up to problematic block then it will stop and execute Premix.
Premix then will launch browser to display a report page. If premix failed to open your default browser,
you can see the report page by opening `premix/index.html`.
In the browser, you can try to navigate tracing result and find where the problem/bug is. In the browser, you can try to navigate tracing result and find where the problem/bug is.
## Helper tools ## Helper tools
* Persist Tool * Persist Tool
Because nimbus p2p layer still contains bugs, you may become impatient when try to syncing blocks. In `/premix` directory, you can find a `persist.nim` tool. It will help you to sync relative quicker because it will bypass p2p layer and download blocks from `geth` via `rpc-api`.
Because nimbus p2p layer still contains bugs, you may become impatient when try to syncing blocks.
In `/premix` directory, you can find a `persist.nim` tool.
It will help you to sync relative quicker because it will bypass p2p layer and download blocks from `geth` via `rpc-api`.
```bash ```bash
nim c -r premix/persist --dataDir:your_database_directory nim c -r premix/persist [--dataDir:your_database_directory] [--head: blockNumber] [--maxBlocks: number] [--numCommits: number]
``` ```
* Debug Tool * Debug Tool
Premix debugging tool also produce a set of debugging meta data that you can use to quickly find the bug without the need to run p2p layer or any other unnecessary code.
Also in `/premix` directory you'll find `debug.nim` tool that you can use to execute this debug meta data and you'll only need to work with one block and one transaction at a time instead of multiple confusing multiple blocks or transactions. Premix debugging tool also produce a set of debugging meta data that you can use to quickly
find the bug without the need to run p2p layer or any other unnecessary code.
In `/premix` directory you'll find `debug.nim` tool that you can use to execute
this debug meta data and you'll only need to work with one block and one transaction
at a time instead of multiple confusing blocks or transactions.
```bash ```bash
nim c -r premix/debug (TODO: more options will come) nim c -r premix/debug blockxxx.json
``` ```
`blockxxx.json` contains database snapshot needed to debug a single block produced by Premix tool.