-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Companion for Use proper bounded vector type for nominations #10601 #4709
Conversation
`MAX_NOMINATIONS` was changed to `MaxNominations`
@georgesdib can you update master here? |
hmm strange companion build failure here. |
Was the build retriggered after my merge for the substrate PR? |
Waiting for commit status. |
The status is a bit weird, what does that mean? Is it stuck checking if the substrate PR merged well? (That PR seems to be in a weird state as well, having successfully merged but then returning a merge error) |
Merge cancelled due to error. Error: Checks failed for 160adf7 |
It required to approve running the jobs, because this was the first time you created a pr. |
* master: Fix incomplete sorting. (#4795) Companion for better way to resolve `Phase::Emergency` via governance #10663 (#4757) Refactor and fix usage of `get_session_index()` and `get_session_info_by_index()` (#4735) `relay chain selection` and `dispute-coordinator` fixes and improvements (#4752) Fix tests (#4787) log concluded disputes (#4785) availability-distribution: look for leaf ancestors within the same session (#4596) Companion for Use proper bounded vector type for nominations #10601 (#4709) Fix release profile (#4778) [ci] remove publish-s3-release (#4779) Companion for substrate#10632 (#4689) [ci] pipeline chores (#4775) New changelog scripts (#4491)
…aritytech#4709) * Fixing polkadot after subtrate changes `MAX_NOMINATIONS` was changed to `MaxNominations` * Fixing some more places * Apply suggestions from code review * update lockfile for {"substrate"} Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com> Co-authored-by: Shawn Tabrizi <shawntabrizi@gmail.com> Co-authored-by: parity-processbot <>
Companion to paritytech/substrate#10601
Renaming
MAX_NOMINATIONS
toMaxNominations
and changing type after changes in substrate in the accompanying PR.@kianenigma