We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Unable to verify any fleet node status by using wakuCanary as the fleet nodes disconnect the canary Node due to not supporting metadata.
./build/wakucanary -a="/dns4/boot-01.ac-cn-hongkong-c.shards.test.status.im/tcp/30303/p2p/16Uiu2HAmGwcE8v7gmJNEWFtZtojYpPMTHy2jBLL6xRk33qgDxFWX"
We should be ping and verify fleet nodes using wakuCanary.
I could observe from fleet logs that test node is disconnected as metadata codec is not supported.
ebe69be8e5f634989bd98fa994149ac874d14b7c I used latest master for the test.
ebe69be8e5f634989bd98fa994149ac874d14b7c
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
As per @vpavlin's recommendation, we need to add the following into the wakucanary app:
wakucanary
nwaku/waku/factory/node_factory.nim
Line 120 in e0079cd
Sorry, something went wrong.
darshankabariya
Successfully merging a pull request may close this issue.
Problem
Unable to verify any fleet node status by using wakuCanary as the fleet nodes disconnect the canary Node due to not supporting metadata.
To reproduce
./build/wakucanary -a="/dns4/boot-01.ac-cn-hongkong-c.shards.test.status.im/tcp/30303/p2p/16Uiu2HAmGwcE8v7gmJNEWFtZtojYpPMTHy2jBLL6xRk33qgDxFWX"
Expected behavior
We should be ping and verify fleet nodes using wakuCanary.
Screenshots/logs
I could observe from fleet logs that test node is disconnected as metadata codec is not supported.
nwaku version/commit hash
ebe69be8e5f634989bd98fa994149ac874d14b7c
I used latest master for the test.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: