Numel and Nbytes Validation (#19121)

[JacobSzwejbka]

Summary:

Attempt 3 to check numel and nbytes overflow. This time we defer checking dynamic sized inputs until their size is realized.

Reviewed By: lucylq

Differential Revision: D98148157

[pytorch-bot]

🔗 Helpful Links

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

• 📄 Preview Python docs built from this PR

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

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• Rolling out OSDC (ARC) runners on pull & trunk workflows in PyTorch main

⏳ 33 Pending, 1 Unrelated Failure

As of commit fc580c8 with merge base cb94506 ():

FLAKY - The following job failed but was likely due to flakiness present on trunk:

• Cadence Build & Test / cpu-test / test-aot / test-aot (gh) (detected as infra flaky with no log or failing log classifier)

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

[meta-codesync]

@JacobSzwejbka has exported this pull request. If you are a Meta employee, you can view the originating Diff in D98148157.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

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