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

Revert "Check flusher interface before calling Flush (#479)" #527

Merged
merged 1 commit into from
Aug 6, 2019

Conversation

johanbrandhorst
Copy link
Contributor

This reverts commit cf7d15a.
This introduced a recursive call to Flush in the proxy, which
will crash the application.

This reverts commit cf7d15a.
This introduced a recursive call to `Flush` in the proxy, which
will crash the application.
@@ -95,7 +90,7 @@ func (w *grpcWebResponse) finishRequest(req *http.Request) {
w.copyTrailersToPayload()
} else {
w.WriteHeader(http.StatusOK)
w.Flush()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@johanbrandhorst whilst we wait for CI to go green on this PR...

...isn't this the root cause of the issue? Shouldn't this be replaced with a safe up-cast on w.wrapped before calling Flush()?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I haven't looked at it in detail, lets discuss after merging the fix.

@jonny-improbable
Copy link
Contributor

Given this failure has had an impact on consumers, it implies we are missing a test. @light0x, would you be in a position to help us contribute a test-case which would help us catch this regression in future, please?

Copy link
Contributor

@jonny-improbable jonny-improbable left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved in order to expedite the fix.

@johanbrandhorst
Copy link
Contributor Author

Rerunning failed tests

@jonny-improbable
Copy link
Contributor

Given that the 2 failures occurred on older versions of Chrome I am happy to chalk the failure down to BrowerStack flakiness and will use Admin powers to merge.

@jonny-improbable jonny-improbable merged commit 4e388ad into master Aug 6, 2019
@jonny-improbable jonny-improbable deleted the revert-479 branch August 6, 2019 11:14
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

Successfully merging this pull request may close these issues.

2 participants