-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
chore(cre-deployment): validate ocr xmission schedule #16265
Conversation
AER Report: CI Core ran successfully ✅AER Report: Operator UI CI ran successfully ✅ |
@@ -148,6 +148,10 @@ func (c *OCR2OracleConfig) UnmarshalJSON(data []byte) error { | |||
} | |||
|
|||
func GenerateOCR3Config(cfg OracleConfig, nca []NodeKeys, secrets deployment.OCRSecrets) (OCR2OracleConfig, error) { | |||
// the transmission schedule is very specific; arguably it should be not be a parameter | |||
if len(cfg.TransmissionSchedule) != 1 || cfg.TransmissionSchedule[0] != len(nca) { | |||
return OCR2OracleConfig{}, fmt.Errorf("transmission schedule must have exactly one entry, matching the len of the number of nodes want [%d], got %v", len(nca), cfg.TransmissionSchedule) |
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.
nca []NodeKeys
excludes the bootstrap node, when called, right?
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, but please fix the keystone test as it fails this validation:
failed to configure contracts: failed to configure OCR3 contract: failed to configure OCR3 contract for don keystone-don: failed to generate OCR3 config: transmission schedule must have exactly one entry, matching the len of the number of nodes want [4], got [1 2 3 4]
|
* chore(cre-deployment): validate ocr xmission schedule * fix tests
Validate the internal OCR capability transmission schedule.
This is the schedule for capability to 'transmit' from the OCR instance to the engine.
We need this to happen right way for all nodes, so the schedule is strictly validated against the number of nodes in the OCR capability DON
Requires
Supports