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
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
acatangiu
changed the title
mmr gadget: make it resilient to finality notifications loss
client/mmr: make it resilient to finality notifications loss
Nov 25, 2022
client/mmr: persisting gadget state across runs
Fixes#12780
* client/mmr: on init do canonicalization catch-up
* client/mmr: add more tests
* client/mmr: persist gadget progress in aux db
* client/mmr: add more tests
* client/mmr: replace async_std with tokio
* remove leftover comment
* address review comments
Signed-off-by: acatangiu <adrian@parity.io>
Repository owner
moved this from Need for Kusama 🗒
to Done ✅
in BEEFYDec 7, 2022
ltfschoen
pushed a commit
to ltfschoen/substrate
that referenced
this issue
Feb 22, 2023
client/mmr: persisting gadget state across runs
Fixesparitytech#12780
* client/mmr: on init do canonicalization catch-up
* client/mmr: add more tests
* client/mmr: persist gadget progress in aux db
* client/mmr: add more tests
* client/mmr: replace async_std with tokio
* remove leftover comment
* address review comments
Signed-off-by: acatangiu <adrian@parity.io>
ark0f
pushed a commit
to gear-tech/substrate
that referenced
this issue
Feb 27, 2023
client/mmr: persisting gadget state across runs
Fixesparitytech#12780
* client/mmr: on init do canonicalization catch-up
* client/mmr: add more tests
* client/mmr: persist gadget progress in aux db
* client/mmr: add more tests
* client/mmr: replace async_std with tokio
* remove leftover comment
* address review comments
Signed-off-by: acatangiu <adrian@parity.io>
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Derived from this comment: https://github.com/paritytech/substrate/pull/12753/files#r1031660875
In-flight finality notifications might get lost on client crashes/restarts. In order to account for this we need to:
The text was updated successfully, but these errors were encountered: