-
Notifications
You must be signed in to change notification settings - Fork 790
Internal code sync #1082
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
Internal code sync #1082
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The generated code with non-closure mode still has MethodInfo so it will definitely break some users.... I think we should update grpc_generator.cc before merging as well(I have a cl for review in critique).
Sounds good. Part of the reason I want to create this PR is to make sure there is no outstanding unmerged (to google3) changes in grpc_generator.cc. Looks like there's none. So we can safely update grpc_generator.cc in google3 now. |
I patched in the But now
Here's roughly how to reproduce locally:
|
Oh man..I guess I know why this fails. I submitted a cl/371207002 internally to fix the closure testing xhrIo..seems like it is not updated in open source? I saw the first line of the error message is "getStreamingResponseHeader, which is what I fixed in closure lib. |
I see. Our grpc-web third_party/closure-library link is currently at v20201102 released on Nov 17, 2020. Your fix was merged late Apr 2021 so we should watch out for the next 2021 May release to see if your fix is included in there. |
3921d6a
to
6cee2fa
Compare
This is getting out of hand. will start to bisect from an older state to see if we can isolate which internal CL causes these errors. |
author:@Jennnnny