-
-
Notifications
You must be signed in to change notification settings - Fork 872
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
Update fix for Issue #555 #559
Conversation
abraunegg
commented
Jun 27, 2019
- Update fix for Successive 504 errors cause crash on third error, even if well spaced in time #555 as try | catch block for session creation appears to miss error response codes
* Update fix for #555 as try | catch block for session creation appears to miss error response codes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine - when one sets up not to show whitespace changes in github, then it becomes clear so easily ;-) Thanks
* Udate handling when response is not a valid JSON object
yep ... wish there was a way to make that the default! |
@norbusan |
* remove try block and trap for explicit entry earlier
* Update how JSONValue object is determined to be valid
* Add error logging when response is not a valid JSON object
* Clean-up messaging and error logging
@norbusan
On the next run:
This PR fixes:
|
* Simplify check to one statement
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So return values sometimes are not json objects, that is a pain indeed. Thanks for fixing (and great that you can reproduce it!)
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |