You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
We have currently (on v3) validation errors on p2p like this :
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.
The text was updated successfully, but these errors were encountered: