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

Socket validation error : port should be integer #3860

Closed
air1one opened this issue Jun 30, 2020 · 0 comments
Closed

Socket validation error : port should be integer #3860

air1one opened this issue Jun 30, 2020 · 0 comments
Assignees

Comments

@air1one
Copy link
Contributor

air1one commented Jun 30, 2020

We have currently (on v3) validation errors on p2p like this :

Socket data validation error (peer 172.18.0.13) : Response validation failed from peer 172.18.0.13 : [{"ip":"172.18.0.10","port":"4000","ports":{},"version":"3.0.0-next.0","height":3,"latency":2},{"ip":"172.18.0.9","port":"4000","ports":{},"version":"3.0.0-next.0","height":3,"latency":5},{"ip":"172.18.0.12","port":"4000","ports":{"@arkecosystem/core-webhooks":-1,"@arkecosystem/core-api":4003},"version":"3.0.0-next.0","height":3,"latency":6}]

It seems it comes from "port" which needs to be integer (so 4000 instead of "4000") so we need to check where do we get it as string to instead keep it as integer.

The validation error can be seen easily on e2e tests on nodes 1 to 4.

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

No branches or pull requests

2 participants