Issue summary
This issue is related to #2726.
The root cause might be the same but it's not 100% proven at this point, but in both cases sending a message results in a failure.
For this issue, we would like to run the node and send a transaction until a fork is happening simultaneously.
Looking at past CI jobs for send failures, I could only find two:
https://github.com/ChainSafe/forest/actions/runs/6573803867/job/17858117090?pr=3609
https://github.com/ChainSafe/forest/actions/runs/6533513531/job/17739353068
The forest daemon errors are slightly different but close enough (a fork was also happening in the second case).
Task summary
Acceptance Criteria
Other information and links
Lotus mpool implementation. Lotus devs also confirmed that their message pool can handle chain reorgs.
Once we have fixed this issue, we can try to enable the balance check again in the calibnet wallet check script.
Issue summary
This issue is related to #2726.
The root cause might be the same but it's not 100% proven at this point, but in both cases sending a message results in a failure.
For this issue, we would like to run the node and send a transaction until a fork is happening simultaneously.
Looking at past CI jobs for send failures, I could only find two:
https://github.com/ChainSafe/forest/actions/runs/6573803867/job/17858117090?pr=3609
https://github.com/ChainSafe/forest/actions/runs/6533513531/job/17739353068
The forest daemon errors are slightly different but close enough (a fork was also happening in the second case).
Task summary
I managed to reproduce the issue only after around 1500 runs. See Send FIL failed #2726 (comment)
Acceptance Criteria
Other information and links
Lotus mpool implementation. Lotus devs also confirmed that their message pool can handle chain reorgs.
Once we have fixed this issue, we can try to enable the balance check again in the calibnet wallet check script.