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

fix: allow autosharding nodes to get peers #1785

Merged
merged 1 commit into from
Jan 17, 2024

Conversation

adklempner
Copy link
Member

@adklempner adklempner commented Jan 12, 2024

Problem

Solution

Fixes some failing tests in #1756 and stops throwing errors if node is setup to use autosharding

Notes

  • Resolves
  • Related to

@adklempner adklempner requested a review from a team as a code owner January 12, 2024 02:03
Copy link

github-actions bot commented Jan 12, 2024

size-limit report 📦

Path Size Loading time (3g) Running time (snapdragon) Total time
Waku core 32.6 KB (0%) 652 ms (0%) 88 ms (-17.76% 🔽) 739 ms
Waku Simple Light Node 261.87 KB (-0.02% 🔽) 5.3 s (-0.02% 🔽) 320 ms (-8.5% 🔽) 5.6 s
ECIES encryption 31.97 KB (0%) 640 ms (0%) 120 ms (+79.72% 🔺) 760 ms
Symmetric encryption 31.96 KB (0%) 640 ms (0%) 87 ms (-27.57% 🔽) 726 ms
DNS discovery 123.33 KB (0%) 2.5 s (0%) 321 ms (+30.71% 🔺) 2.8 s
Privacy preserving protocols 119.37 KB (0%) 2.4 s (0%) 131 ms (-57.83% 🔽) 2.6 s
Light protocols 30.16 KB (-0.17% 🔽) 604 ms (-0.17% 🔽) 68 ms (-39.11% 🔽) 671 ms
History retrieval protocols 29.07 KB (-0.16% 🔽) 582 ms (-0.16% 🔽) 85 ms (+75.59% 🔺) 666 ms
Deterministic Message Hashing 5.92 KB (0%) 119 ms (0%) 25 ms (+18% 🔺) 143 ms

Copy link
Collaborator

@weboko weboko left a comment

Choose a reason for hiding this comment

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

nit: would be nice to have description for the PR and/or related task

Copy link
Collaborator

@danisharora099 danisharora099 left a comment

Choose a reason for hiding this comment

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

please also add some tests for getConnectedPeers when autosharded params are passed

find static sharding tests for relevance (in packages/tests/tests/getPeers.spec.ts

@adklempner adklempner force-pushed the fix/autosharding-peers branch 2 times, most recently from 74b3c64 to 7a18dc3 Compare January 17, 2024 05:33
@adklempner adklempner force-pushed the fix/autosharding-peers branch from 7a18dc3 to c897ee6 Compare January 17, 2024 16:20
@adklempner
Copy link
Member Author

@danisharora099 added test cases for getPeers with js-waku configured for autosharding

@danisharora099 danisharora099 merged commit 4dd451b into feat/shard-peer-selection Jan 17, 2024
8 of 10 checks passed
@danisharora099 danisharora099 deleted the fix/autosharding-peers branch January 17, 2024 18:55
danisharora099 added a commit that referenced this pull request Jan 19, 2024
* merge: master

* fix: tests

* update: interfafces

* rm: comments

* metadata: store peerIdStr instead of peerId

* chore(utils): move fast-utils to dev deps

* fix: allow autosharding nodes to get peers (#1785)

* fix: merge

* fix: build

* fix: failing tests from master merge

---------

Co-authored-by: Arseniy Klempner <arseniyk@status.im>
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.

3 participants