-
Notifications
You must be signed in to change notification settings - Fork 72
Switching to TorchServe for 1.6.0 inference has caused undocumented breaking changes and regression #85
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
Enabled debugging in
|
@setu4993
|
@amaharek : Thank you for identifying what needs to be fixed and actually showing a PoC! From looking at the changes, I think it would work, though I'm not sure how to try it :/. What I'd like, though, is this not being applied to include just other files but everything in Would you be willing to submit a PR with the changes you've made above to this repo? If yes, that'd be great and I hope the maintainers would be willing to accept it. I'd be happy to add to it to add the functionality I describe above. |
@amaharek |
This issue happens to all pytorch inference containers > 1.6.0 |
I understand that you are not sure how to test the above code on your end. Also, you want to include all files in the directory To test the above change, I have extended the aws container and created a new one in my account as following:
Please check this sample notebook for more information about extending aws containers. The above change ensures all files in I have already made a PR and hopefully it will be merged. Thanks |
Thank you very much @amaharek, your PR changes worked for me. I'm using 1.7.1 and my approach was the following, if it helps anyone else out.
Dockerfile:
Example:
I am now packing all dependencies in the model.tar.gz archive, rather than dealing with source_dir or dependencies parameters, which are confusing and unnecessary. The structure of model.tar.gz is as follows:
The extra_lib, which I need to access from my inference.py is available in /opt/ml/model/code/extra_lib. Hopefully this fix gets merged soon so others do not have to spend a ton of time debugging.. |
Happy to know that it worked for you @dectl I think the reason why the parameters like When you create the |
This issue was fixed in TS0.3.1 and toolkitv2.0.5.. These fixes are available in latest SM DLC. |
See aws/sagemaker-python-sdk#1909.
The text was updated successfully, but these errors were encountered: