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
This test published a contract and waits for a series of events to occur. Unfortunately after looking at the logs of the nightly integration tests they timeout waiting for such events to arrive on the WS. I managed to replicate the issue locally by re-running that single test twice and extended the logs in the code to print the problem:
After looking further into the logs, the rejection is due to an incorrect check in the code. The optimistic insert of c0e03d4e-76f7-498c-ae75-97b1945a6ab2 fails, and the code concludes this is because it conflicts with existing record 1305816f-660a-40d3-9a8b-59c5ab465c68.
This is not correct. Actually c0e03d4e-76f7-498c-ae75-97b1945a6ab2 is being published after being a previously-local-only FFI - meaning that the insert fails because of an ID conflict, which should take it down this branch to reconcile the published details with the local record:
Item 1305816f-660a-40d3-9a8b-59c5ab465c68 is actually not a conflict at all. It has the same name but a different version. Seems to simply be an error in how we are interpreting insert errors.
I was investigating the reason for the integration tests failing nightly and trying to fix them. I came across this E2E test https://github.com/hyperledger/firefly/blob/main/test/e2e/multiparty/ethereum_contracts.go#L331 which was constantly failing.
This test published a contract and waits for a series of events to occur. Unfortunately after looking at the logs of the nightly integration tests they timeout waiting for such events to arrive on the WS. I managed to replicate the issue locally by re-running that single test twice and extended the logs in the code to print the problem:
It seems that there is a conflict when we try and publish the FFI.
The text was updated successfully, but these errors were encountered: