Skip to content
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

Merged
merged 2 commits into from
Feb 7, 2025

Conversation

krehermann
Copy link
Contributor

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

@krehermann krehermann requested review from a team as code owners February 6, 2025 18:40
@krehermann krehermann requested review from Tofel and bolekk February 6, 2025 18:41
@krehermann krehermann enabled auto-merge February 6, 2025 18:42
Copy link
Contributor

github-actions bot commented Feb 6, 2025

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

@@ -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)
Copy link
Contributor

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?

@Tofel Tofel self-requested a review February 7, 2025 10:44
Tofel
Tofel previously requested changes Feb 7, 2025
Copy link
Contributor

@Tofel Tofel left a 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] 

@krehermann krehermann added this pull request to the merge queue Feb 7, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Feb 7, 2025
@krehermann krehermann added this pull request to the merge queue Feb 7, 2025
Merged via the queue into develop with commit b3fb706 Feb 7, 2025
183 of 187 checks passed
@krehermann krehermann deleted the cre/ocr-transmisson-bug branch February 7, 2025 19:43
karen-stepanyan pushed a commit that referenced this pull request Feb 10, 2025
* chore(cre-deployment): validate ocr xmission schedule

* fix tests
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants