🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/157929

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit the bot commands wiki or our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 4b6fd57 with merge base e3f2597 ():
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@albanD I made the equivalent change as the torch gather issue #157425. Let me know if you want any additional changes.

I updated the PR after some local testing following your lead. The case is similar to gather, except the original tensor is returned when index is empty.

@pytorchbot merge

PR targets viable/strict rather than main, refusing merge request

@pytorchbot merge

Merge failed

Reason: This PR needs a release notes: label
If your changes are user facing and intended to be a part of release notes, please use a label starting with release notes:.

If not, please add the topic: not user facing label.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "topic: not user facing"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.

Didn't find following labels among repository labels: release,notes:,python_frontend

@pytorchbot label "release notes: python_frontend"

@pytorchbot merge

Merge started

Your change will be merged once all checks pass (ETA 0-4 Hours).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team