machinefi / sprout

sprout
Apache License 2.0
16 stars 13 forks source link

[BUG] Default env settings not getting applied #257

Closed simonerom closed 4 months ago

simonerom commented 4 months ago

Describe the bug When enode/znode doesn't connect to the database, other errors happen on start. It seems that config values used to be in docker-compose.yaml have been removed and now they do not get applied. This PR https://github.com/machinefi/sprout/commit/5fcb8a062f76e957b19886970cad65b4734a283f is when the config has been removed from docker-compose.yaml. They have been moved to the Viper package, yet the default values are not applied to my system.

To Reproduce Steps to reproduce the behavior:

Make sure you are in a clean system (i.e. Sprout config values such as CHAIN_ENDPOINT, DATABASE_DSN and similar config is not already set on your system)

git clone https://github.com/machinefi/sprout && cd sprout
git checkout v0.6.0
docker compose up -d

Check the Sprout logs (znode cannot connect to the DB, even though the DB seems to be running correctly). Check screenshots below.

Expected behavior Be able to send messages to Sprout.

Screenshots img_v3_0285_a07744c2-c279-4eed-8ac3-1da453c960dh

img_v3_0285_8ad96937-6765-4cc3-9315-4be932ee459h

Versions (please complete the following information):

Additional context Add any other context about the problem here.

simonerom commented 4 months ago

Fixed in 0.6.1