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

Add proxy support for SSE transport #79

Merged
merged 3 commits into from
Apr 17, 2019
Merged

Add proxy support for SSE transport #79

merged 3 commits into from
Apr 17, 2019

Conversation

sjung-stripe
Copy link
Contributor

For #78 . Also had to fix an issue with the httmock dependency being pulled into non-test environments. We'd like this to go into a released version, if possible - it's blocking an internal issue and we'd rather not use a git version if we can avoid it.

@sjung-stripe
Copy link
Contributor Author

@sjung-stripe
Copy link
Contributor Author

ah, it appears your tests need httmock to be in requirements.txt or otherwise it doesn't get installed. i'll fix that, but if you have other opinions on how to arrange this, do let me know

@cory-signalfx
Copy link
Contributor

/cc @rmfitzpatrick

@sjung-stripe
Copy link
Contributor Author

ah, and this build failure is because your tests depend on a secure envar (SIGNALFX_API_TOKEN); travis doesn't export that envar into the PR's tests because my branch is on a fork. nothing i can do about that one

setup.py parses everything in requirements.txt and adds it to
install_requires, so httmock was being pulled into the package
dependencies even though it's only needed for tests.

(Also, it's spelled "tests_require", not "test_requires".)
Copy link
Contributor

@mpetazzoni mpetazzoni left a comment

Choose a reason for hiding this comment

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

Looks great! Thanks a lot for sending a PR for this!

I know about the test not being able to run in PRs. Thanks for fixing httmock though!

@sjung-stripe
Copy link
Contributor Author

Had to add another change here. It seems your API now returns errorType and context keys in the JSON when the execute endpoint receives an error. The code was splatting the entire JSON into the initializer for the SignalFlowException, which caused python to throw a type error on the unrecognized kwargs.

@mpetazzoni mpetazzoni merged commit cfbda55 into signalfx:master Apr 17, 2019
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