Add quick fix for view/inplace issue with DDP

[albanD]

As per title, temporary mitigation for #46242 for which #46296 will be a proper fix.

[facebook-github-bot]

💊 CI failures summary and remediations

As of commit b99dea7db6 (more details on the Dr. CI page):

---

💚 💚 Looks good so far! There are no failures yet. 💚 💚

---

This comment was automatically generated by Dr. CI (expand for details).

Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions on the GitHub issue tracker or post in the (internal) Dr. CI Users group.

See how this bot performed.

This comment has been revised 2 times.

[dr-ci]

💊 CI failures summary and remediations

As of commit ff92b96 (more details on the Dr. CI page):

---

✅ None of the CI failures appear to be your fault 💚

---

• 1/1 broken upstream at merge base 908c235 on Oct 15 from 8:28am to 12:15pm PDT (9 commits; 7580962 - 8c26111)

---

🚧 1 fixed upstream failure:

These were probably caused by upstream breakages that were already fixed.

Please rebase on the viable/strict branch (expand for instructions)

If your commit is newer than viable/strict, you can try basing on an older, stable commit:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase --onto FETCH_HEAD $(git merge-base origin/master HEAD)

If your commit is older than viable/strict:

git fetch https://github.com/pytorch/pytorch viable/strict
git rebase FETCH_HEAD

Check out the recency history of this "viable master" tracking branch.

• binary_linux_libtorch_3_7m_cpu_devtoolset7_shared-with-deps_build on Oct 15 from 8:28am to 12:15pm PDT (9 commits; 7580962 - 8c26111)
  • 🔁 rerun

---

This comment was automatically generated by Dr. CI (expand for details).

Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions on the GitHub issue tracker or post in the (internal) Dr. CI Users group.

See how this bot performed.

This comment has been revised 8 times.

[gchanan]

I thought the case that couldn't be handled was multiple view outputs.

[albanD]

For custom Function it's any number of output views.
For regular (codegened) functions, it only multi-output.

[facebook-github-bot]

@albanD has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

[facebook-github-bot]

@albanD merged this pull request in 849bc77.