Skip to content

Fix indirect streaming messages.#58

Merged
drichelson merged 1 commit into
masterfrom
dr/indirect
Oct 21, 2016
Merged

Fix indirect streaming messages.#58
drichelson merged 1 commit into
masterfrom
dr/indirect

Conversation

@drichelson

@drichelson drichelson commented Oct 21, 2016

Copy link
Copy Markdown
Contributor

Fix indirect streaming messages. I ran the integration harness with these changes (including a big feature flag that triggers an indirect/put) and it passed.

Comment thread ldclient/streaming.py

@staticmethod
def process_message(store, requester, msg, ready):
payload = json.loads(msg.data)

@drichelson drichelson Oct 21, 2016

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The indirect message data fields are not json, but instead are a list of flag keys (or one flag key in the case of indirect/patch). We were failing here when attempting to parse the json.

example:

event: indirect/patch
data: big.00.bigFeatureKey

@drichelson drichelson changed the title Fix indirect streaming messages Fix indirect streaming messages. Oct 21, 2016
@jkodumal

Copy link
Copy Markdown
Contributor

👍

@pkaeding

Copy link
Copy Markdown
Contributor

lgtm
👍
looks good to me
merge away
I approve
canned replies are great.

@drichelson drichelson merged commit b9fc62a into master Oct 21, 2016
@drichelson drichelson deleted the dr/indirect branch October 21, 2016 04:46
eli-darkly added a commit that referenced this pull request Jun 12, 2018
re-add missing clear method to user keys cache
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.

3 participants