github-actions[bot]
commented
2 months ago size-limit report 📦
| Path | Size | Loading time (3g) | Running time (snapdragon) | Total time |
|---|---|---|---|---|
| Waku node | 180.93 KB (0%) | 3.7 s (0%) | 3.2 s (+47.25% 🔺) | 6.8 s |
| Waku Simple Light Node | 180.85 KB (0%) | 3.7 s (0%) | 2.5 s (-8.65% 🔽) | 6.1 s |
| ECIES encryption | 23.08 KB (0%) | 462 ms (0%) | 584 ms (-8.37% 🔽) | 1.1 s |
| Symmetric encryption | 22.55 KB (0%) | 452 ms (0%) | 878 ms (+67.08% 🔺) | 1.4 s |
| DNS discovery | 72.42 KB (0%) | 1.5 s (0%) | 2.9 s (+101.84% 🔺) | 4.4 s |
| Peer Exchange discovery | 74.1 KB (0%) | 1.5 s (0%) | 1.3 s (-33.71% 🔽) | 2.8 s |
| Local Peer Cache Discovery | 67.64 KB (0%) | 1.4 s (0%) | 967 ms (-49.12% 🔽) | 2.4 s |
| Privacy preserving protocols | 38.87 KB (0%) | 778 ms (0%) | 1.3 s (+26.18% 🔺) | 2.1 s |
| Waku Filter | 111.42 KB (0%) | 2.3 s (0%) | 1.8 s (-16.35% 🔽) | 4.1 s |
| Waku LightPush | 110.11 KB (0%) | 2.3 s (0%) | 2.7 s (+30.87% 🔺) | 4.9 s |
| History retrieval protocols | 110.72 KB (0%) | 2.3 s (0%) | 1.6 s (-25.89% 🔽) | 3.9 s |
| Deterministic Message Hashing | 4.83 KB (0%) | 97 ms (0%) | 70 ms (+17.81% 🔺) | 167 ms |
Problem
In order for the node to discover and connect to new peers different than the fleets, we should be in
cluster-id1 and subscribed to some shard.This would fix the failing js-optional tests
Issue
Advances https://github.com/waku-org/nwaku/issues/2621