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.

Sign up for GitHub

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

Jump to bottom

exec: protect against unset syncFlowConsumer #38557

Merged
merged 1 commit into from
Jul 8, 2019
Merged

exec: protect against unset syncFlowConsumer #38557

merged 1 commit into from
Jul 8, 2019

Commits on Jun 28, 2019

  1. exec: protect against unset syncFlowConsumer 

    This should never happen since it implies that the receiver isn't
connected correctly. These happen when a node sends a SetupFlow request
to a remote node where the spec specifies that the response is on that
remote node. We don't see panics in the row execution engine due to
wrapping the syncFlowConsumer with a copyingRowReceiver, but this state
can cause setupVectorized to panic.

This commit protects against this state pending further investigation.

Release note: None
    @asubiotto
    asubiotto committed Jun 28, 2019
    Configuration menu
    Copy the full SHA
    08cc37d View commit details
    Browse the repository at this point in the history