-
Notifications
You must be signed in to change notification settings - Fork 740
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
Remove ValidateFromChainState #5707
Conversation
239c401
to
7989ec9
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.
I love where it's going, first we removed jaeger, then a subsystem message variant, now I eagerly await when we start to remove whole subsystems :)
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! LGTM!
# Description This PR removes the `CandidateValidationMessage::ValidateFromChainState`, which was previously used by backing, but is no longer relevant since initial async backing implementation paritytech/polkadot#5557. Fixes #5643 ## Integration This change should not affect downstream projects since `ValidateFromChainState` was already unused. ## Review Notes - Removed all occurrences of `ValidateFromChainState`. - Moved utility functions, previously used in candidate validation tests and malus, exclusively to candidate validation tests as they are no longer used in malus. - Deleted the `polkadot_parachain_candidate_validation_validate_from_chain_state` metric from Prometheus. - Removed `Spawner` from `ReplaceValidationResult` in malus’ interceptors. - `fake_validation_error` was only used for `ValidateFromChainState` handling, while other cases directly used `InvalidCandidate::InvalidOutputs`. It has been replaced with `fake_validation_error`, with a fallback to `InvalidCandidate::InvalidOutputs`. - Updated overseer’s minimal example to replace `ValidateFromChainState` with `ValidateFromExhaustive`.
Description
This PR removes the
CandidateValidationMessage::ValidateFromChainState
, which was previously used by backing, but is no longer relevant since initial async backing implementation paritytech/polkadot#5557.Fixes #5643
Integration
This change should not affect downstream projects since
ValidateFromChainState
was already unused.Review Notes
ValidateFromChainState
.polkadot_parachain_candidate_validation_validate_from_chain_state
metric from Prometheus.Spawner
fromReplaceValidationResult
in malus’ interceptors.fake_validation_error
was only used forValidateFromChainState
handling, while other cases directly usedInvalidCandidate::InvalidOutputs
. It has been replaced withfake_validation_error
, with a fallback toInvalidCandidate::InvalidOutputs
.ValidateFromChainState
withValidateFromExhaustive
.