NotificationsYou must be signed in to change notification settings
Fork696
Star1.5k

Change to TORCH_CHECK_VALUE for sparse ops#5215

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Closed

spcyppt wants to merge1 commit intopytorch:mainfromspcyppt:export-D88918840

Closed

Change to TORCH_CHECK_VALUE for sparse ops#5215

spcyppt wants to merge1 commit intopytorch:mainfromspcyppt:export-D88918840

+11 −8

Conversation

Copy link

Contributor

spcyppt commentedDec 11, 2025

Summary:
X-link:https://github.com/facebookresearch/FBGEMM/pull/2212

Change to useTORCH_CHECK_VALUE for sparse ops so that the error can be correctly classified correctly and avoid unnecessary job retries.

Reviewed By: q10

Differential Revision: D88918840

Copy link

Contributor

meta-codesyncbot commentedDec 11, 2025

@spcyppt hasexported this pull request. If you are a Meta employee, you can view the originating Diff inD88918840.

meta-clabot added the cla signed label

Dec 11, 2025

meta-codesyncbot added fb-exported meta-exported labels

Dec 11, 2025

Use TORCH_CHECK_VALUE in sparse ops (pytorch#5215)

ef46156

Summary:X-link:facebookresearch/FBGEMM#2212Change to use [`TORCH_CHECK_VALUE`](https://fburl.com/code/xxeanfi2) for sparse ops so that the error can be correctly classified correctly and avoid unnecessary job retries.Reviewed By: q10Differential Revision: D88918840