You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 29, 2020. It is now read-only.
I wanted to keep you in the loop in case it is an issue with the latest version of discovery-cli (0.1.8) using the "develop" docker images.
The README says to change the docker tag to "develop," when using multiple worker nodes. I also tried running with NODES=3 discovery start but got the same error(s).
NOTE:
I did an uninstall of discovery-cli with npm uninstall -g @enigmampc/discovery-cli
removed all discovery docker images (including orphaned and dangling)
Fresh install with npm install -g @enigmampc/discovery-cli
Hi @lacabra, I added this issue to the salad repo (mistakenly): scrtlabs/salad#50
and just closed it with a resolution of changing the
.envto use the "latest" docker images instead of "develop."I'm not sure if this is an issue with using the "develop" docker images at this point, or some other element in my or the OP's configuration/environment. From the dev forum: https://forum.enigma.co/t/salad-some-integration-tests-fail/1243/6.
I wanted to keep you in the loop in case it is an issue with the latest version of
discovery-cli(0.1.8) using the "develop" docker images.The README says to change the docker tag to "develop," when using multiple worker nodes. I also tried running with
NODES=3 discovery startbut got the same error(s).NOTE:
npm uninstall -g @enigmampc/discovery-clinpm install -g @enigmampc/discovery-clidiscovery initusing 'SW'-
discovery startdiscovery stopbuilddirectorydiscovery start