Update reference to torch::TypeError#72
Conversation
|
@mehtanirav Thanks for the PR! Looks good to me. For some reason clang-tidy is complaining about code complexity in an unrelated part of the code base. Do you mind disabling |
|
Hi @mehtanirav! Thank you for your pull request. We require contributors to sign our Contributor License Agreement, and yours needs attention. You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
What does this PR do? Please describe:
Following the changes in pytorch/pytorch#87855, we want to update references to
torch:TypeErrortoTORCH_CHECK_TYPE. The changes are already made to fbcode in internal diffFixes #{issue number}
Does your PR introduce any breaking changes? If yes, please list them:
List of all backwards-incompatible API changes.
Check list: