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

CapabilityRegistry updates #13183

Merged
merged 34 commits into from
May 27, 2024

Conversation

cds95
Copy link
Contributor

@cds95 cds95 commented May 13, 2024

No description provided.

@cds95 cds95 requested a review from a team as a code owner May 15, 2024 13:44
@cds95 cds95 force-pushed the use-encode-instead-of-encode-packed-capability-id branch from 70ea5d9 to be9ccf5 Compare May 20, 2024 10:55
DeividasK
DeividasK previously approved these changes May 23, 2024
@cl-sonarqube-production
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

Copy link
Contributor

@bolekk bolekk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The title of the PR doesn't really match the contents - there's way more stuff here than just "encode packed" :)

struct DONCapabilityConfig {
/// @notice The set of p2pIds of nodes that belong to this DON. A node (the same
// p2pId) can belong to multiple DONs.
EnumerableSet.Bytes32Set nodes;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The order here is not fixed. I wonder if this could cause any problems with OCR, where order of the nodes is important. I think OCR's config will just handle that but still a little concerned.

@DeividasK DeividasK changed the title encode instead of encode packed for capability id CapabilityRegistry updates May 27, 2024
@DeividasK DeividasK added this pull request to the merge queue May 27, 2024
@DeividasK
Copy link
Collaborator

The title of the PR doesn't really match the contents - there's way more stuff here than just "encode packed" :)

Fair fair, updated 🙂

@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 27, 2024
@DeividasK DeividasK added this pull request to the merge queue May 27, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks May 27, 2024
@archseer archseer added this pull request to the merge queue May 27, 2024
Merged via the queue into develop with commit 9630475 May 27, 2024
107 checks passed
@archseer archseer deleted the use-encode-instead-of-encode-packed-capability-id branch May 27, 2024 10:49
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