Skip to content

Add raw_data option for event_stream method#189

Merged
solarkennedy merged 2 commits intothefactory:masterfrom
fengyehong:raw-event-stream
Apr 19, 2017
Merged

Add raw_data option for event_stream method#189
solarkennedy merged 2 commits intothefactory:masterfrom
fengyehong:raw-event-stream

Conversation

@fengyehong
Copy link
Copy Markdown
Contributor

This is just a proposal. If you just store events in a message queue and leave it to other consumers, then there is no need to parse the event data as MarathonEvent object

@solarkennedy
Copy link
Copy Markdown
Contributor

How but just raw instead of raw_data? But Yea I would merge

@fengyehong
Copy link
Copy Markdown
Contributor Author

updated and rebased

@solarkennedy
Copy link
Copy Markdown
Contributor

Why is travis not testing this?...

When handling events asynchronously, you may just want to put
event data in a message queue, so getting raw data here is a small
optimization that saves parsing and serializing event data.
@fengyehong
Copy link
Copy Markdown
Contributor Author

Why is travis not testing this?...

No idea

@solarkennedy
Copy link
Copy Markdown
Contributor

I've asked travisci and @mbabineau to turn it off and on again.

In the mean time can you run the tests locally via tox and confirm that they pass?

@fengyehong
Copy link
Copy Markdown
Contributor Author

In fact, I have received Travis build success email for my forked repo

https://github.com/fengyehong/marathon-python/branches

@solarkennedy solarkennedy merged commit 1e78725 into thefactory:master Apr 19, 2017
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