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
Let torch.sign support complex types #43243
Conversation
The rule follows those of NumPy: https://numpy.org/doc/stable/reference/generated/numpy.sign.html [ghstack-poisoned]
The rule follows those of NumPy: https://numpy.org/doc/stable/reference/generated/numpy.sign.html [ghstack-poisoned]
💊 CI failures summary and remediationsAs of commit 9fb4ce3 (more details on the Dr. CI page):
🚧 1 ongoing upstream failure:These were probably caused by upstream breakages that are not fixed yet:
ci.pytorch.org: 1 failedThis 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. This comment has been revised 19 times. |
The rule follows those of NumPy: https://numpy.org/doc/stable/reference/generated/numpy.sign.html [ghstack-poisoned]
The rule follows those of NumPy: https://numpy.org/doc/stable/reference/generated/numpy.sign.html ghstack-source-id: 4fa51ec548e904dffc48a3f4d8ab54d632d48e81 Pull Request resolved: #43243
The rule follows those of NumPy: https://numpy.org/doc/stable/reference/generated/numpy.sign.html [ghstack-poisoned]
The rule follows those of NumPy: https://numpy.org/doc/stable/reference/generated/numpy.sign.html ghstack-source-id: 9904d9cfd158cb49cc2276ad21b05de7c2c50029 Pull Request resolved: #43243
OK, thanks. Let me change this to a warning message PR. Looking forward to your implementation! |
New PR opened: #43280 Abandoning this one now |
Stack from ghstack:
The rule follows those of NumPy: https://numpy.org/doc/stable/reference/generated/numpy.sign.html