-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[parachain] Second meetup in bootstrap.py --test
fails due to 0 attestees
#391
Comments
bootstrap.py --test
fails due to 0 attestees
Hmm, it could be that we just have a phase issue, this in this run we see that only one attestation makes it onchain and 2 are discarded due to wrong phase: https://github.com/encointer/encointer-parachain/actions/runs/12842890953/job/35814334830 |
Is it maybe because waiting for inblock is not enough, and we need finalized to get a consistent result? |
In the zombienet integration test they simply allow invalid tx's, as they are the result of a tx already included in another block: https://github.com/paritytech/zombienet/blob/cf4d25153cfa50b516dc718003311dc56d6a3611/javascript/packages/orchestrator/src/jsapi-helpers/chainUpgrade.ts#L132. Maybe, our problem is that the send attestations are in a block, which gets rejected, and in the meantime we include the next-phase tx. If our sent-attestations tx's are then included in a canonical block, we get the error that attestation phase is required. Hence, the possible solution is to accept tx-status invalid and to wait longer to make sure that our tx's are in the canonical chain. |
We observe this only on the parachain, and there it is consistent.
The CLI does consistently say 0 attestees:
Reproduce with:
zombienet-linux-x64 spawn --provider native zombienet/rococo-local-with-encointer.toml
./bootstrap_demo_community.py --signer //Alice -w collective -b 7 --test
The text was updated successfully, but these errors were encountered: