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
We should probably add a runtime API to expose information about current MBMs.
There are lots of events to follow what is happening, but for just querying whether a migration is ongoing, it is required to read storage directly.
The RAPI should expose something like this:
traitMbm{/// Whether there are migrations currently running.fnongoing() -> MbmIsOngoing;/// The current progress. Returns `Some(_)` iff `ongoing()` is either `Ongoing` or `Stuck`.fnprogress() -> Option<MbmProgress>;/// The prefices that are being migrated and possibly not decodable during this time.fnaffected_prefices() -> Vec<Vec<u8>>;// from https://github.com/paritytech/polkadot-sdk/issues/6128}enumMbmIsOngoing{Ongoing,NotOngoing,Stuck,}structMbmProgress{/// Index of the currently running migration.current_migration:u32,/// Number of total migrations that will run.total_migrations:u32,/// Number of steps that the current migration already took.current_migration_steps:u32,/// Number of steps that the current migration is allowed to take at most.current_migration_max_steps:u32,}
I woul wait with this issue once #6128 is settled.
The text was updated successfully, but these errors were encountered:
We should probably add a runtime API to expose information about current MBMs.
There are lots of events to follow what is happening, but for just querying whether a migration is ongoing, it is required to read storage directly.
The RAPI should expose something like this:
I woul wait with this issue once #6128 is settled.
The text was updated successfully, but these errors were encountered: