Currently when a future is resolved and a result is made, the result is put in both the start and end nodes. But in the start node, if the future is passed to another agent in a separate instance, that agent would be subscribed as a consumer in the start node, but would never receive the result when done.
There is currently a function in future.py, like send_result that sends the results to all the consumers. The current logic currently doesn't have the start node executing this send_result function to all its consumers, which is why the effort level is set to low.
Basically just call this function when the result is received by the start node.
Currently when a future is resolved and a result is made, the result is put in both the start and end nodes. But in the start node, if the future is passed to another agent in a separate instance, that agent would be subscribed as a consumer in the start node, but would never receive the result when done.
There is currently a function in future.py, like send_result that sends the results to all the consumers. The current logic currently doesn't have the start node executing this send_result function to all its consumers, which is why the effort level is set to low.
Basically just call this function when the result is received by the start node.