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

2.2.1 release #1536

Merged
merged 4 commits into from
Mar 28, 2017
Merged

2.2.1 release #1536

merged 4 commits into from
Mar 28, 2017

Conversation

shin-
Copy link
Contributor

@shin- shin- commented Mar 28, 2017

List of PRs / issues for this release

Bugfixes

  • Fixed a bug where the status_code attribute of APIError exceptions would
    not reflect the expected value.
  • Fixed an issue where the events method would time out unexpectedly if no
    data was sent by the engine for a given amount of time.

alex-dr and others added 4 commits March 28, 2017 14:48
requests.Response objects evaluate as falsy when the status_code
attribute is in the 400-500 range. Therefore we are assured that
prior to this change, APIError would show `is_server_error() == False`
when generated with a 500-level response and `is_client_error() == False`
when generated with a 400-level response. This is not desirable.

Added some seemingly dry (not DRY) unit tests to ensure nothing silly
slips back in here.

Signed-off-by: alex-dr <[email protected]>
@shin- shin- added this to the 2.2.1 milestone Mar 28, 2017
@shin- shin- merged commit 599aa1a into release Mar 28, 2017
@shin- shin- deleted the 2.2.1-release branch November 2, 2017 22:34
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