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

Initial Python websocket-client to the Resourcer #1

Merged
merged 3 commits into from
Mar 15, 2016
Merged

Conversation

randompi
Copy link
Contributor

What's this PR do?

Uses the websocket-client module to handle connections to the resourcer and a framework for handling the connection and forwarding messages on to the bot app that will use this connection.

Where should the reviewer start?

See changelist.

How should this be manually tested?

Follow instructions in README, start sample app. Also export LOG_LEVEL=DEBUG. Stop dev-console process, verify that the app client tries to reconnect in a randomized exponential backoff fashion, with max retry backoff at 32 seconds.

Any background context you want to provide?

Made the change to get the retry open websocket connection on close from:
websocket-client/websocket-client#95

Screenshots (if appropriate)

http://i.imgur.com/8dVeY.jpg

Then do `pip install requirements.txt`

You will need the following env vars set. In Prod, these would be passed in via Beep Boop.

Copy link
Contributor

Choose a reason for hiding this comment

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

More of a reminder... when we point to the Resourcer-dev, we'll want to add instructions on how they fetch these values from the beepboophq site.

@chris-skud
Copy link
Contributor

This looks great. So happy retry memory profile is flat as a pancake.

👍

randompi added a commit that referenced this pull request Mar 15, 2016
Initial Python websocket-client to the Resourcer
@randompi randompi merged commit be4d1ca into master Mar 15, 2016
@randompi randompi deleted the initial branch March 15, 2016 15:32
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