Describe the bug
When running the network with more than one worker node, there seems to be a mismatch with the workerSelection algorithm implementation between EnigmaJS and P2P, as they disagree on what worker is assigned to what task
To Reproduce
Steps to reproduce the behavior:
Launch the network with NODES set to a value greater than 1: NODES=2 ./launch.bash
Run any number of integration tests, and soon enough this error will appear.
Expected behavior
Both implementations should agree, and the computations sent to the selected worker should succeed.
Backtrace
The only relevant network output is as follows:
p2p_1 | [Wed May 01 2019 19:52:36 GMT+0000 (Coordinated Universal Time)] INFO [VERIFY_NEW_TASK] error in verification of task 88987af7d35eabcad95915b93bfd3d2bc3308f06b7197478b0dfca268f0497dc: WorkerSelectionVerificationErr: Not the selected worker for the 88987af7d35eabcad95915b93bfd3d2bc3308f06b7197478b0dfca268f0497dc task
p2p_1 | [Wed May 01 2019 19:52:36 GMT+0000 (Coordinated Universal Time)] DEBUG [VERIFY:] task 88987af7d35eabcad95915b93bfd3d2bc3308f06b7197478b0dfca268f0497dc not verified
Desktop (please complete the following information):
Describe the bug When running the network with more than one worker node, there seems to be a mismatch with the workerSelection algorithm implementation between EnigmaJS and P2P, as they disagree on what worker is assigned to what task
To Reproduce Steps to reproduce the behavior:
NODES
set to a value greater than 1:NODES=2 ./launch.bash
Expected behavior Both implementations should agree, and the computations sent to the selected worker should succeed.
Backtrace The only relevant network output is as follows:
Desktop (please complete the following information):