This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
Adds checking for the word 'unauthorized' to the unauthorized check. #171 #174
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Yeah I think to support all versions and unexpected encounters this is what we'll have to do until some sort of consistency is provided back from the db with regards to errors. |
|
Pulled in, 1.4.5 released. |
|
Thanks a lot! |
jonhyman
added a commit
to jonhyman/moped
that referenced
this pull request
May 3, 2013
arthurnn
pushed a commit
that referenced
this pull request
Aug 6, 2013
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Looking at the error message I've been having,
failed with error "unauthorized"and then looking at errors.rb,#error_messageit seems like there was neither a code nor an assertionCode in the response.As such, I decided to regex the error message for the word unauthorized. A bit shady perhaps, but I'm getting this error frequently and sporadically in production and staging after upgrading to 2.4.1. :-\