Skip to content

Conversation

@NickCraver
Copy link
Collaborator

In investigating an issue in #1989, I found a few gaps. Overall:

  1. Twemproxy has an out of date CommandMap, which propagated to Envoy.
  2. We were expecting both interactive and subscription connections to complete to complete the async handler...but we shouldn't because subscriptions may be disabled.
  3. RedisSubscriber changes on the sync path weren't validating the message (asserting the command map has it enabled).

This fixes all of the above and adds another test considering all 3.

In investigating an issue in #1989, I found a few gaps. Overall:
1. Twemproxy has an out of date CommandMap, which propagated to Envoy.
2. We were expecting both interactive and subscription connections to complete to complete the async handler...but we shouldn't because subscriptions may be disabled.
3. RedisSubscriber changes on the sync path weren't validating the message (asserting the command map has it enabled).

This fixes all of the above and adds another test considering all 3.
Copy link
Contributor

@rkarthick rkarthick left a comment

Choose a reason for hiding this comment

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

LGTM

@NickCraver NickCraver merged commit 5e2b43c into main Feb 22, 2022
@NickCraver NickCraver deleted the craver/connection-fixes branch February 22, 2022 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants