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

1.2.4 #105

Merged
merged 12 commits into from
Mar 4, 2019
Merged

1.2.4 #105

merged 12 commits into from
Mar 4, 2019

Conversation

tchellomello
Copy link
Owner

@tchellomello tchellomello commented Mar 4, 2019

tchellomello and others added 12 commits June 16, 2018 02:04
If last retry resulted in an error the command method did not raise an exception, but rather logged, e.g., "Trying again due error 401" followed by "Query worked. Exit code: 401". Now if all attempts, including all retries, result in errors, an exception will be raised. Also changed log messages for request errors to warnings, except for on last retry, which is logged as an error.
Fix command error handling after last retry
Create a dictionary of sessions, with max_retries as key, so they can be reused once created. Also _retries_conn and _timeout_protocol usage was not thread safe; fix that.
Missed changing one occurence of self._retries_conn to retries in command method.
@coveralls
Copy link

coveralls commented Mar 4, 2019

Coverage Status

Coverage increased (+0.3%) to 32.98% when pulling 479f0f7 on 1.2.4 into 4a2d9f9 on amcrest-1.2.x.

@tchellomello tchellomello merged commit 97278fc into amcrest-1.2.x Mar 4, 2019
@tchellomello tchellomello deleted the 1.2.4 branch March 4, 2019 04:57
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