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
I have observed that FireFly Core and EVMConnect have trouble communicating the very first batch/ack after FireFly Core restarts. EVMConnect thinks that the WebSocket client disconnects right after dispatching the batch, but it receives the ack from FireFly Core right after that, but it's too late because it's already marked the attempt as failed, so it tries again. FireFly Core correctly discards the duplicate event and ack's it again. The cycle repeats and finally succeeds the third time.
Steps to reproduce
Create a new FireFly stack and run a few transactions that will result in a batch pin
docker restart your FireFly core container
Do another transaction from the other FireFly node
Description
I have observed that FireFly Core and EVMConnect have trouble communicating the very first batch/ack after FireFly Core restarts. EVMConnect thinks that the WebSocket client disconnects right after dispatching the batch, but it receives the
ack
from FireFly Core right after that, but it's too late because it's already marked the attempt as failed, so it tries again. FireFly Core correctly discards the duplicate event and ack's it again. The cycle repeats and finally succeeds the third time.Steps to reproduce
docker restart
your FireFly core containerFireFly Core Log
EVMConnect Log
The text was updated successfully, but these errors were encountered: