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
With v0.33.0-rc2 test we see, that new PeerExchange RPC is not decoded well when request coming from clients using protocol the old way.
Missing response field is identified as error in case of request RPC.
status.staging fleet testing v0.33.0-rc2 has thousands of this error, no PeerExchange is working there now.
Response field shall not be handled as mandatory for requests.
v0.33.0-rc2
The text was updated successfully, but these errors were encountered:
Fixed with PR #3055 https://grafana.infra.status.im/d/qrp_ZCTGz/nim-waku-v2?var-host=.%2A&var-fleet=status.staging&var-dc=All status.staging with v0.33.0-rc3 deployed now serving PX requests.
Sorry, something went wrong.
NagyZoltanPeter
No branches or pull requests
Problem
With v0.33.0-rc2 test we see, that new PeerExchange RPC is not decoded well when request coming from clients using protocol the old way.
Impact
Missing response field is identified as error in case of request RPC.
To reproduce
status.staging fleet testing v0.33.0-rc2 has thousands of this error, no PeerExchange is working there now.
Expected behavior
Response field shall not be handled as mandatory for requests.
Screenshots/logs
nwaku version/commit hash
v0.33.0-rc2
The text was updated successfully, but these errors were encountered: