Eduard S b59f790c04 Use init SC vars and start block from events Previously the Synchronizer required the initial variables of the smart contracts to be passed as a configuration parameter (that the node took from the configuration file). The same applied to the blockNumber. The last update of the smart contracts introduced events for each smart contract constructor (initializer), which allows querying the initial variables as well as the initial block number for each smart contract. Now the synchronizer uses this information, and thus the initial variables and the starting block numbers have been removed from the configuration.		4 years ago
.github/workflows	Rm unused ETHCLIENT_DIAL_URL	4 years ago
api	Fix format of the MTP for exit endpoint	4 years ago
apitypes	Wrap all errors with tracerr	4 years ago
batchbuilder	Extend Coordinator tests	4 years ago
cli/node	Use init SC vars and start block from events	4 years ago
common	Update txs constructors and helpers	4 years ago
config	Use init SC vars and start block from events	4 years ago
coordinator	Use init SC vars and start block from events	4 years ago
db	Effective amounts add missing checks	4 years ago
eth	Use init SC vars and start block from events	4 years ago
log	Use tracerr call traces in log	4 years ago
node	Use init SC vars and start block from events	4 years ago
priceupdater	Wrap all errors with tracerr	4 years ago
prover	Add mock proof server	4 years ago
synchronizer	Use init SC vars and start block from events	4 years ago
test	Use init SC vars and start block from events	4 years ago
txselector	TxSelector add CoordIdxDB, SelectionConfig, abstract filtering	4 years ago
.gitignore	Implement first iteration of node	4 years ago
README.md	Rm unused ETHCLIENT_DIAL_URL	4 years ago
go.mod	Upgrade contracts and parse init events	4 years ago
go.sum	Upgrade contracts and parse init events	4 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