-
Notifications
You must be signed in to change notification settings - Fork 243
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
PyTorch Hub models and dependencies should be versioned #63
Comments
@nlothian Hub provides a way to pin to a specific release branch by We're planning to add some version information on the website, our CI will be testing against latest stable releases(torch/torchvision). |
Thanks. Is there a way to know what version I should pin against? And is that dependency transitive somehow? |
Unfortunately the latest Pytorch release doesn't stay static (you all keep on working on things!!), and we'd love not to have to keep debugging these types of version issues everytime our pipeline breaks. We're fine to upgrade to latest now, but we don't like having to keep doing it whenever we bring up a new instance that does a |
We are using the PyTorch deeplabv3_resnet101 model on AWS (on pytorch 1.1), and it suddenly stopped working.
It appears that a recent upgrade to torchvision/inception (!) broke this model:
Is there a way to avoid this?
The text was updated successfully, but these errors were encountered: