-
Notifications
You must be signed in to change notification settings - Fork 1.6k
collect included disputes from on-chain #3924
Conversation
803ec4c
to
6d716d7
Compare
6d716d7
to
b8cf3cd
Compare
b8cf3cd
to
1b6a837
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Only needs implementers guide changes.
Co-authored-by: Robert Habermeier <rphmeier@gmail.com>
return Ok(()) | ||
}, | ||
Ok(Err(e)) => { | ||
tracing::debug!( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As this probably can come from a runtime upgrade, it should probably be warn
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it should be debug
IMO otherwise the logs will constantly be filled with warn!
until we upgrade the runtime to include this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fair, but should we make it warn
once the runtime got upgraded? Follow up issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
.validators | ||
.get(validator_index.0 as usize) | ||
.or_else(|| { | ||
tracing::error!( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Looks pretty good! |
@@ -41,6 +42,7 @@ const SESSION_INFO_CACHE_SIZE: usize = 64 * 1024; | |||
const DMQ_CONTENTS_CACHE_SIZE: usize = 64 * 1024; | |||
const INBOUND_HRMP_CHANNELS_CACHE_SIZE: usize = 64 * 1024; | |||
const CURRENT_BABE_EPOCH_CACHE_SIZE: usize = 64 * 1024; | |||
const ON_CHAIN_VOTES_CACHE_SIZE: usize = 3 * 1024; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any reason for choosing 3KiB for cache size? the lowest we have is 64KiB, but it's not really backed by data
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No particular reason. We simply won't use it that much, so this could be an optimization to remove it.
bot merge |
Trying merge. |
TODO:
runtime_impl::imported_disputes()
-fns.imported_disputes
on the node side, so older runtime versions that do not provide the call, do not take down the node.