-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Specifying image_uri in PyTorchModel gives TypeError when running deploy #2202
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
Comments
I was able to replicate the bug with the following system information:
Also reported it to AWS support on the 20th of May. |
Affects me as well, workaround seems to be to just provide a dummy version, but an annoying bug all the same. |
Same to me! |
Same for me. For the huggingface predictor it actually works, but it doesn't use the image I built but rather the default one... |
Update: After figuring out how to work with the repository for sagemaker images I was able to get my problems fixed (which have been solely regarding the |
Hi |
As far as I remember I just added the parameter I can't believe that this issue is still open. The way how AWS issues get ignored by Amazon developers is rather disappointing. |
Thanks this seems to work for me as well.... |
Me looking at my inbox and laughing frenetically: No. |
Does your |
@Michael-Bar
|
Hi all, #3188 partially has addressed the problem. Still, some ambiguity remains for the specification of |
Closing as fixed by #3188 |
Describe the bug
When creating a PyTorchModel and deploying to endpoint, using a specified
image_uri
, the model object is has attributeself.framework_version=None
. In the check for_is_mms_version
this will cause an error because of running a regex search with an input of type None instead of string or byte.To reproduce
Expected behavior
I expect the behavior to be the same as when providing
framework_version
andpy_version
into the creation of a PyTorchModelScreenshots or logs
System information
A description of your system. Please provide:
Thanks
The text was updated successfully, but these errors were encountered: