-
Notifications
You must be signed in to change notification settings - Fork 10
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
refactor: change eth-pm using lightnode, filter to now use relay #148
Conversation
Yep that's expected as we only connect to one peer by default. We can change that once we have implement Waku peer exchange, did some dog fooding of DNS Discovery and run a second operator trial to ensure there are enough nodes to connect to. |
Gotcha ok! Also, not sure why the CI hasn't executed on these yet 🤔 |
"start": "react-scripts start", | ||
"build": "react-scripts build", | ||
"eject": "react-scripts eject", | ||
"start": "GENERATE_SOURCEMAP=false PORT=3001 craco start", |
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.
Oooh, does this remove all the sourcemap warnings? Interesting. I did do some upstream PR to help with those ChainSafe/js-libp2p-gossipsub#337
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.
Yes, this doesn't generate sourcemap altogether; don't think we need it in our case.
eth-pm/package.json
Outdated
"@ethersproject/shims": "^5.5.0", | ||
"@types/craco__craco": "^6.4.0", |
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.
Where do you use the typing?
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.
I was trying to initiialise craco.config.js in ts instead so installed types, but ended up reverting to js because of some weird bugs and, from what it looked like, the lack of TS support on craco.
Pushed a commit to remove this as a dependency.
Please confirm you tested locally and it still works. |
Not sure what is going with the CI checks. Let's see if they get triggered when you force push after signing |
Not sure why the build on the CI is failing -- it builds fine for me locally 👀 |
Best to look at the logs to understand the failure:
I am guessing you did not commit changes to the |
ok fixed - can merge it now @fryorcraken |
@danisharora099 some commits are not signed and I can't easily resign your commits (I am assuming there's a merge commit in there?). I'd suggest you squash, sign and push. |
rm: source map generation for build rm: unused dependency sign commmit add: pnpm-lock rm: comment refactor: change eth-pm using lightnode, filter to now use relay
98ad43c
to
2c3a8af
Compare
Ignore that, I squashed and signed. |
This PR addresses #88:
filter
andstore
to now usingrelay
TODO/confirm:
waku.relay.getPeers()
does not return a number more than 1 for some reason