Restore call convention compatibility in get_model#304
Uh oh!
There was an error while loading. Please reload this page.
Conversation
This file contains hidden or 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
A bug surfaced where first time evaluation of a model fails due to the Model constructor throwing if the model does not exist. Looking deeper, we see that most calls to get_model expect a possible None response and check at the call site. Unfortunately we get the same WebserviceException class for a model not being found as we do a REST error or similar. This change is a stopgap mitigation to restore compatibility with the existing callers, and compromises by allowing the model version dependent behavior to continue passing on exceptions. In a future follow up we should settle on a convention and allow version checks to propagate failure while still giving the possibility for handling a service exception in the caller.
j-so approved these changes Jul 3, 2020
Comment on lines +62 to +65
| # TODO(tcare): Finding a specific version currently expects exceptions | ||
| # to propagate in the case we can't find the model. This call may | ||
| # result in a WebserviceException that may or may not be due to the | ||
| # model not existing. |
Contributor
There was a problem hiding this comment.
Deployment isn't using this method - why WebserviceException? It should be just the training and batch scoring pipeline that uses this.
Contributor
There was a problem hiding this comment.
Nevermind - I see what you're saying. Can you make a new issue for this?
Contributor
j-so commented Jul 3, 2020
LGTM - can you run the batch scoring pipeline to make sure this doesn't affect that (it shouldn't, but just to be sure)? |
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment
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.
A bug surfaced where first time evaluation of a model fails due to the Model constructor throwing if the model does not exist.
Looking deeper, we see that most calls to get_model expect a possible None response and check at the call site. Unfortunately we get the same WebserviceException class for a model not being found as we do a REST error or similar.
This change is a stopgap mitigation to restore compatibility with the existing callers, and compromises by allowing the model version dependent behavior to continue passing on exceptions.
In a future follow up we should settle on a convention and allow version checks to propagate failure while still giving the possibility for handling a service exception in the caller.