Skip to content

stop suggesting using guard_size_oblivious on data dependent errors#160510

Closed
laithsakka wants to merge 2 commits intogh/laithsakka/260/basefrom
gh/laithsakka/260/head
Closed

stop suggesting using guard_size_oblivious on data dependent errors#160510
laithsakka wants to merge 2 commits intogh/laithsakka/260/basefrom
gh/laithsakka/260/head

Conversation

@laithsakka
Copy link
Contributor

@laithsakka laithsakka commented Aug 13, 2025

[ghstack-poisoned]
@laithsakka laithsakka requested a review from bobrenjc93 as a code owner August 13, 2025 07:49
@pytorch-bot
Copy link

pytorch-bot bot commented Aug 13, 2025

🔗 Helpful Links

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

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

✅ No Failures

As of commit 75388ad with merge base a8d6943 (image):
💚 Looks good so far! There are no failures yet. 💚

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

desc = "Could not guard on data-dependent expression"
size_oblivious_result_msg = (
"consider using data-dependent friendly APIs such as "
"guard_or_false, guard_or_true and statically_known_true"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this still here?

Copy link
Contributor Author

@laithsakka laithsakka Aug 15, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am suggesting "guard_or_false, guard_or_true and statically_known_true"
instead of suggesting guard_size_oblivious.
maybe user on code data dependent errors or things we did not handle yet,

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess I would probably advise NOT giving a suggestion (or linking to docs) if it requires user discretion to figure out how to resolve. Because otherwise someone will just blindly paste the suggested call in without understanding what it does.

@laithsakka laithsakka changed the title stop suggeting using guard_size_oblivious on data dependent errors stop suggesting using guard_size_oblivious on data dependent errors Aug 15, 2025
…nt errors"

cc ezyang SherlockNoMad EikanWang jgong5 wenzhe-nrv

[ghstack-poisoned]
laithsakka added a commit that referenced this pull request Sep 2, 2025
@laithsakka
Copy link
Contributor Author

@pytorchbot merge

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Sep 2, 2025
@pytorchmergebot
Copy link
Collaborator

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

Advanced Debugging
Check the merge workflow status
here

@pytorchmergebot
Copy link
Collaborator

Merge failed

Reason: 1 jobs have failed, first few of them are: inductor / inductor-cpu-build / build

Details for Dev Infra team Raised by workflow job

@laithsakka
Copy link
Contributor Author

@pytorchbot merge -i "not related"

@pytorch-bot
Copy link

pytorch-bot bot commented Sep 3, 2025

❌ 🤖 pytorchbot command failed:

@pytorchbot: error: unrecognized arguments: not related

usage: @pytorchbot [-h] {merge,revert,rebase,label,drci,cherry-pick} ...

Try @pytorchbot --help for more info.

@laithsakka
Copy link
Contributor Author

@pytorchbot merge -i

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged while ignoring the following 1 checks: inductor / inductor-cpu-build / build

Learn more about merging in the wiki.

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

Advanced Debugging
Check the merge workflow status
here

markc-614 pushed a commit to markc-614/pytorch that referenced this pull request Sep 17, 2025
mansiag05 pushed a commit to mansiag05/pytorch that referenced this pull request Sep 22, 2025
dsashidh pushed a commit to dsashidh/pytorch that referenced this pull request Sep 26, 2025
@github-actions github-actions bot deleted the gh/laithsakka/260/head branch October 4, 2025 02:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/inductor ciflow/trunk Trigger trunk jobs on your pull request fx Merged release notes: fx release notes category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants