The 1.5 release branch has been cut!
This issue is for tracking cherry-picks to the release branch. The criteria for a change to be included is ALL of the following:
If you need a change to be cherry-picked to the branch, please open a PR against the release/1.5 branch and comment below. Any details you can provide about the criteria above (e.g. links to master PR, description of the severity of the bug fix) are helpful. Ultimately we will make an inclusion / no inclusion call and communicate that here.
NOTE: do not land the PRs yourself. Our normal tools (ghstack / ghimport, etc.) do not work on the release branch. Someone else will land your change for you.
Docs change once it lands https://github.com/pytorch/pytorch/pull/35007
EDIT: release/1.5 PR https://github.com/pytorch/pytorch/pull/35043
This was included when we fast forwarded the release branch.
This was included when we fast forwarded the release branch.
@jamesr66a: looks good to go, can you open a PR against the release branch?
https://github.com/pytorch/pytorch/pull/35340 may be a candidate. Autocasting completes Pytorch's native automatic mixed precision support, which I've been writing for over 6 months now targeting 1.5. It has thorough documentation and test coverage. It was approved and merged already, but reverted for minor fixes.
Update: PR against master https://github.com/pytorch/pytorch/pull/35102 has been re-merged and stuck the landing so far. https://github.com/pytorch/pytorch/pull/35340 cherry-picks those diffs onto 1.5 (+3 lines of cosmetic docstring changes).
Feature, sorry :(. It's in nightlies though.
C++ frontend fixes:
Cherry-picked into 1.5:
Merged
~https://github.com/pytorch/pytorch/pull/35133~
^We'd like to get this in because it aligns torchbind's qualified names with the custom op API, and sets us up to converge the two in the future. Getting this into 1.5 would allow us to save a lot of BC headache in the future
EDIT: Was reverted. Will update with superseding PR soon
EDIT2: Updated PR https://github.com/pytorch/pytorch/pull/35303
Merged
Leaving it here because this PR fixes a high priority issue. This PR adds Support for Tensor Shape Type Hint.
This made the release branch.
https://github.com/pytorch/pytorch/pull/35275
^ Load torch_global_deps for Windows
EDIT: Was abandoned. Will update with superseding PR soon
Abandoned
Merged
^ Load all DLLs in the lib directory for Windows
Merged
Ready patches for PTD:
~#35262~ #35514 enforce rref JIT pickling to be in the scope of rpc calls (port for #34689)
~#35264~ #35513 Enforce rref python pickling to be in the scope of RPC call (port for #34755)
WIP doc patches for PTD:
Merged non-WIP patches.
cc @zhaojuanmao @rohan-varma
Merged
https://github.com/pytorch/pytorch/pull/35349 was opened as a port for https://github.com/pytorch/pytorch/pull/35144.
Merged.
test_torchscript_functions_not_supported
failure on the release branch. (port for #35283)cc @xush6528
Merged
https://github.com/pytorch/pytorch/pull/35406, port of #35131.
https://github.com/pytorch/pytorch/pull/35405, port of https://github.com/pytorch/pytorch/pull/35231.
https://github.com/pytorch/pytorch/pull/35407, port of #35053.
Merged all.
https://github.com/pytorch/pytorch/pull/35412
^ To add future
as a dependency for all of our packages
Merged
https://github.com/pytorch/pytorch/pull/35413 bump up ONNX exporter's version (original: https://github.com/pytorch/pytorch/pull/35059)
https://github.com/pytorch/pytorch/pull/35416 fix torch.mm in ONNX exporter (original: https://github.com/pytorch/pytorch/pull/34661)
Merged
https://github.com/pytorch/pytorch/pull/35434 contains doc strings and documentation updates for channels last
Merged
Merged
Merged
https://github.com/pytorch/pytorch/pull/35657, port of https://github.com/pytorch/pytorch/pull/35560: fixes torch.real and torch.imag
Merged
35340 may be a candidate. Autocasting completes Pytorch's native automatic mixed precision support, which I've been writing for over 6 months now targeting 1.5. It has thorough documentation and test coverage. It was approved and merged already, but reverted for minor fixes.
Update: PR against master #35102 has been re-merged and stuck the landing so far. #35340 cherry-picks those diffs onto 1.5 (+3 lines of cosmetic docstring changes).
Feature, sorry :(. It's in nightlies though.
Hi @mcarilli , so is it going to merge into 1.5 or we can only get it from 1.6 nightly buid? (there is no 1.5 nightly build now)
Merged
@wenhui-prudencemed Looks like autocast won't be merged to 1.5, because it it's a new feature (fails to satisfy 1. in Greg's original post).
You can use it via nightlies or master now. See master documentation:
https://pytorch.org/docs/master/amp.html
https://pytorch.org/docs/master/notes/amp_examples.html
https://github.com/pytorch/pytorch/pull/35579 Disabling complex construction because we want to release all complex related features in 1.6
Merged
https://github.com/pytorch/pytorch/pull/35745 adds a warning that 1.5's implementation of automatic mixed precision is incomplete and points people to the master branch/nightly builds.
Merged
Ready for cherry-pick:
std::abs
instead of abs
in lbfgs.cpp (cherry-pick PR: https://github.com/pytorch/pytorch/pull/36033)Merged
https://github.com/pytorch/pytorch/pull/35808, port of #35109. Only touches RPC documentation
Merged
Merged
https://github.com/pytorch/pytorch/pull/36111
Fixes python type annotations for torchbind types in certain situations
Merged
https://github.com/pytorch/pytorch/pull/36116 (Errored)
https://github.com/pytorch/pytorch/pull/36338 (Fixed errors)
Update docs for 1.5 to remove Python 2 references
Merged
fixed issue #36046.
Merged
https://github.com/pytorch/pytorch/pull/36126, port of https://github.com/pytorch/pytorch/pull/36052
Current plan is not to cherry-pick it; we want more signal / work done on the warning mechanism.
https://github.com/pytorch/pytorch/pull/36165
Group libraries in docs table of contents and add link to new PyTorch Elastic page
Merged
https://github.com/pytorch/pytorch/pull/36245, port of https://github.com/pytorch/pytorch/pull/36161 C++ Adam optimizer - corrected messages for check of default options.
Merged
https://github.com/pytorch/pytorch/pull/36274, port of https://github.com/pytorch/pytorch/pull/35601 fix is_float_scale_factor warning (python and c++)
Merged
Not sure if this is the right place, but I would consider issue #36378 to be a blocker for release, as for example it prevents building torchvision.
https://github.com/pytorch/pytorch/pull/36514
minor change to fix formatting errors in the warnings added by https://github.com/pytorch/pytorch/pull/35745.
Merged
Any possibility of sneaking #35352 into 1.5.0?
Nope, feature.
AT_CHECK is gone, what's alternative?
Add a warning for Single-Process Multi-GPU DDP
Merged
AT_CHECK is gone, what's alternative?
@jinfagang TORCH_CHECK is the alternative.
Any possibility of sneaking #35352 into 1.5.0?
No, this is a feature.
Merged
Doc-only change to make sure existing URLs to RPC docs are still valid.
Merged
@gchanan
https://github.com/pytorch/pytorch/pull/36824
Given that we keep running into the issue of incredibly long compilation times, we decided to switch to the simple executor which skips fusion-related passes and analyses. It might affect some users that rely on fusion on GPU to achieve their performance. profile. We will make a note in our release notes for such users to enable the profiling executor.
Merged
@mrshenli Is this issue getting tracked for release? https://github.com/pytorch/pytorch/issues/36268
PR https://github.com/pytorch/pytorch/pull/36523
https://github.com/pytorch/pytorch/pull/36839, which fixes https://github.com/pytorch/pytorch/issues/36798.
Didn't make it, documented in known issues.
disable flaky test #36924
Merged
https://github.com/pytorch/pytorch/pull/36927 fixes xla job failure on release/1.5 branch. (CI only change)
Merged
@gchanan https://github.com/pytorch/pytorch/pull/36933 should fix the test failures
Merged, but didn't make the RC. So if we do another release or RC it will be in, but otherwise we'll have some known test failures.
Fixes build error when USE_DISTRIBUTED=0
. This does not need to be added into our release binaries as they are all built with USE_DISTRIBUTED=1
, but needs to be landed into the release/1.5
source branch in case users would like to build using USE_DISTRIBUTED=0
.
Didn't make it, this seems minor.
@mrshenli Is this issue getting tracked for release? https://github.com/pytorch/pytorch/issues/36268
PR https://github.com/pytorch/pytorch/pull/36523
No, we weren't confident in the fix so close to the release.
Most helpful comment
https://github.com/pytorch/pytorch/pull/35340 may be a candidate. Autocasting completes Pytorch's native automatic mixed precision support, which I've been writing for over 6 months now targeting 1.5. It has thorough documentation and test coverage. It was approved and merged already, but reverted for minor fixes.
Update: PR against master https://github.com/pytorch/pytorch/pull/35102 has been re-merged and stuck the landing so far. https://github.com/pytorch/pytorch/pull/35340 cherry-picks those diffs onto 1.5 (+3 lines of cosmetic docstring changes).
Feature, sorry :(. It's in nightlies though.