Handle wrong library ProblemDetailException (PP-1860) #2170
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.
Description
Handle
ProblemDetailException
that results when a patron tries to log into the wrong library.Because of the way the tests mocked things, there were a few changes to the tests to make sure the right function gets mocked.
Motivation and Context
By far the most common unhandled exception we are seeing from the webserver is this one:
It occurs when trying to log into the wrong library. It seems like maybe Aspen has some users misconfigured, since many of these requests originate from them.
This is causing unnecessary alerts, since this is an "expected" exception in this case, so we handle the exception.
How Has This Been Tested?
Checklist