Closed EnriqueL8 closed 7 months ago
Fixed by creating a token pool correctly in the Firefly Performance CLI https://github.com/hyperledger/firefly-perf-cli/pull/79
Actually fixed by https://github.com/hyperledger/firefly-transaction-manager/pull/116
As part of https://github.com/hyperledger/firefly/issues/1470, I've noticed that the broadcast where not getting confirmed or just stuck.
I ran a first test and this first screenshot already shows something odd from
577e8c47680c6230209a74829921a9c427766af8
:The pending graph is negative, so we have more confirmed than sent odd.
I then pulled down 1.3.0-rc1 and run another test to see
It just gets stuck and again more confirmed than submitted.. I opened up the UI and all the broadcast messages were stuck in Pending but the private message were going through.
Digged into the logs and found the following:
and
Clearly there is a Batch that is stuck somewhere, I then traversed more logs and found:
Unfortunately I cleared the above run, and ran the same commit of 1.3.0-rc1 and got the same problem, but found some news logs
Two things that I then investigated: