test: Add a quick test to see if newaddr over grpc-web-proxy works
#562
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cdecker
force-pushed
the
202501-newaddr-grpc-repro
branch
from
a41161d to
3d8e02f
Compare
cdecker
force-pushed
the
202501-newaddr-grpc-repro
branch
from
3d8e02f to
e58b40c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@ShahanaFarooqui reports that the
newaddrmethod returns a notimplemented. This is my attempt to reproduce the issue,
unsuccessfully. I wonder if this is a mixup in the interfaces: we
might accidentally be talking to the
schedulerrather than thenode. Any grpc server will return anunimplementederror formethods that are not in their schema, hence a mixup could cause this.