-
Notifications
You must be signed in to change notification settings - Fork 58
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
release: v1.9.1 #462
release: v1.9.1 #462
Conversation
Staleness Report: 1.9.1(gpu)
Staleness Report: 1.9.1(cpu)
|
Failed tests
Confirmed that these failed with the issues tracked
pytorch succeeded when reran |
conda-forge::fastapi[version='>=0.110.3,<0.111.0'] | ||
conda-forge::uvicorn[version='>=0.30.1,<0.31.0'] | ||
conda-forge::pytorch-gpu[version='>=2.0.0,<2.1.0'] | ||
conda-forge::tensorflow-gpu[version='>=2.14.0,<2.15.0'] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this introduced recently?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah in 1.9.0 we switched to fix the gpu issue in 1.8. From 2.0 we switch back to standard tensorflow
May not related to this PR. But why in staleness report, |
Since this is a patch release, the latest relevant version would be latest patch from v2.0. So since there's no 2.0.1, 2.0.0 is latest "relevant" version |
Do we need the change to remove conda default channel and use conda-forge only in Docker file? |
No, we're doing that change from 2.0. For v1 since it's breaking change we are keeping it the same |
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.