Eduard S 20b8d0561f Update synchronizer and DB with last contracts updates - API - When updating network info, handle cases where no batches exists and where no forgers exists - cli/node - Update `cfg.buidler.toml` config file to a working version - common - Add new smart contract structs and extend some existing ones to reflect updates regarding events from the smart contracts - SQL - Add new tables and extend existing ones to reflect updates regarding events from the smart contracts - db/historydb - Add functions to insert new smart contract events data - Fix unclosed rows that led to inconsistent sql driver state (replace NamedQuery by NamedExec). This fixes the error: `pq: unexpected Parse response 'C'` - db/l2db - Close rows after usage - eth - In Rollup event, introduce a new UpdateBucketsParameter when there's a SafeMode event, with `SafeMode = true` - synchronizer - synchronize new events - avoid calling `auction.CanForge` before the genesisBlock to avoid getting a revert.		3 years ago
.github/workflows	Rm unused ETHCLIENT_DIAL_URL	3 years ago
api	Update synchronizer and DB with last contracts updates	3 years ago
apitypes	Wrap all errors with tracerr	3 years ago
batchbuilder	Wrap all errors with tracerr	3 years ago
cli/node	Update synchronizer and DB with last contracts updates	3 years ago
common	Update synchronizer and DB with last contracts updates	3 years ago
config	Simplify prover client, use big.Int in Proof	3 years ago
coordinator	Update synchronizer and DB with last contracts updates	3 years ago
db	Update synchronizer and DB with last contracts updates	3 years ago
eth	Update synchronizer and DB with last contracts updates	3 years ago
log	Use tracerr call traces in log	3 years ago
node	Update node and coordinator, fix linters	3 years ago
priceupdater	Wrap all errors with tracerr	3 years ago
prover	Simplify prover client, use big.Int in Proof	3 years ago
synchronizer	Update synchronizer and DB with last contracts updates	3 years ago
test	Update synchronizer and DB with last contracts updates	3 years ago
txselector	Integrate purger to node	3 years ago
.gitignore	Implement first iteration of node	3 years ago
README.md	Rm unused ETHCLIENT_DIAL_URL	3 years ago
go.mod	StateDB ZKInputs generation compatible with circom	3 years ago
go.sum	StateDB ZKInputs generation compatible with circom	3 years ago

README.md

hermez-node

Go implementation of the Hermez node.

Test

First run a docker instance of the PostgresSQL (where yourpasswordhere should be your password)

POSTGRES_PASS=yourpasswordhere; sudo docker run --rm --name hermez-db-test -p 5432:5432 -e POSTGRES_DB=hermez -e POSTGRES_USER=hermez -e POSTGRES_PASSWORD="$POSTGRES_PASS" -d postgres

Then, run the tests with the password as env var

POSTGRES_PASS=yourpasswordhere go test -p 1 ./...

NOTE: -p 1 forces execution of package test in serial. Otherwise they may be executed in paralel and the test may find unexpected entries in the SQL databse because it's shared among all tests.

There is an extra temporal option that allows to run the API server through the Go tests. This should be removed once the API can be properly initialized, with data from the synchronizer and so on. To use this, run FAKE_SERVER=yes POSTGRES_PASS=yourpasswordhere go test -timeout 0 ./api -p 1 -count 1 -v

Lint

Install golangci-lint
Once installed, to check the lints

golangci-lint run --timeout=5m -E whitespace -E gosec -E gci -E misspell -E gomnd -E gofmt -E goimports -E golint --exclude-use-default=false --max-same-issues 0