-
Notifications
You must be signed in to change notification settings - Fork 768
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
approval-voting: finality stalls in zombienet test 0006-parachains-max-tranche0
#3826
Labels
I2-bug
The node fails to follow expected behavior.
Comments
cc @ordian |
sandreim
changed the title
approval-voiting: finality stalls in
approval-voting: finality stalls in Mar 25, 2024
zombienet test 0006-parachains-max-tranche0
zombienet test 0006-parachains-max-tranche0
3 tasks
Additional data point: https://gitlab.parity.io/parity/mirrors/polkadot-sdk/-/jobs/5637724 in #3805 fails for same reason
|
2 tasks
This seems to affect also
Thx! |
github-merge-queue bot
pushed a commit
that referenced
this issue
Mar 26, 2024
Fixes #3826. The docs on the `candidates` field of `BlockEntry` were incorrectly stating that they are sorted by core index. The (incorrect) optimization was introduced in #3747 based on this assumption. The actual ordering is based on `CandidateIncluded` events ordering in the runtime. We revert this optimization here. - [x] verify the underlying issue - [x] add a regression test --------- Co-authored-by: Bastian Köcher <git@kchr.de>
github-project-automation
bot
moved this from In Progress
to Completed
in parachains team board
Mar 26, 2024
dharjeezy
pushed a commit
to dharjeezy/polkadot-sdk
that referenced
this issue
Apr 9, 2024
…tytech#3831) Fixes paritytech#3826. The docs on the `candidates` field of `BlockEntry` were incorrectly stating that they are sorted by core index. The (incorrect) optimization was introduced in paritytech#3747 based on this assumption. The actual ordering is based on `CandidateIncluded` events ordering in the runtime. We revert this optimization here. - [x] verify the underlying issue - [x] add a regression test --------- Co-authored-by: Bastian Köcher <git@kchr.de>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Looks like optimizations done in #3747 are causing a finality stall. I have reverted locally and confirmed this PR introduced it, but haven't really looked for a solution.
What is specific in this test is that
needed_approvals
is set ton_validators - 1
assuming backing groups of 1.Additionally
0001-parachains-pvf
test is also affected by same issue.First issue which causes the stall:
2024-03-25 15:05:41.001 WARN tokio-runtime-worker parachain::approval-voting: Failed to create assignment bitfield block_hash=0x2879a329794ab4bd147508f837d7245bce2cc22f3e102331dc865c1a4ebb9e29 err=NullAssignment
Second issue which can disrupt connectivity and hinder approval vote propagation
The text was updated successfully, but these errors were encountered: