Skip to content

Fix usage of forwarding references#161094

Closed
lakshayg wants to merge 2 commits intopytorch:mainfrom
lakshayg:forward-issues
Closed

Fix usage of forwarding references#161094
lakshayg wants to merge 2 commits intopytorch:mainfrom
lakshayg:forward-issues

Conversation

@lakshayg
Copy link
Copy Markdown
Collaborator

@lakshayg lakshayg commented Aug 20, 2025

I found a number of places that seem to want forwarding
references but the type signature does not reflect that

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel @mingfeima @XiaobingSuper @ashokei @jingxu10 @jerryzh168 @aditew01

@pytorch-bot
Copy link
Copy Markdown

pytorch-bot Bot commented Aug 20, 2025

🔗 Helpful Links

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

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

❌ 1 New Failure

As of commit 9cc5aec with merge base a0136f1 (image):

NEW FAILURE - The following job has failed:

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

@pytorch-bot pytorch-bot Bot added module: cpu CPU specific problem (e.g., perf, algorithm) NNC release notes: quantization release notes category labels Aug 20, 2025
@facebook-github-bot facebook-github-bot added the oncall: jit Add this issue/PR to JIT oncall triage queue label Aug 20, 2025
@lakshayg lakshayg marked this pull request as ready for review August 21, 2025 20:44
@soulitzer soulitzer added the triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module label Aug 26, 2025
@malfet
Copy link
Copy Markdown
Contributor

malfet commented Aug 26, 2025

@pytorchbot merge

@pytorch-bot pytorch-bot Bot added the ciflow/trunk Trigger trunk jobs on your pull request label Aug 26, 2025
@pytorchmergebot
Copy link
Copy Markdown
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
Copy Markdown
Collaborator

Merge failed

Reason: 1 jobs have failed, first few of them are: trunk / win-vs2022-cpu-py3 / build

Details for Dev Infra team Raised by workflow job

@lakshayg
Copy link
Copy Markdown
Collaborator Author

@pytorchmergebot rebase

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

Successfully rebased forward-issues onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout forward-issues && git pull --rebase)

@lakshayg
Copy link
Copy Markdown
Collaborator Author

@pytorchmergebot rebase

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

@pytorchbot started a rebase job onto refs/remotes/origin/viable/strict. Check the current status here

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

Successfully rebased forward-issues onto refs/remotes/origin/viable/strict, please pull locally before adding more changes (for example, via git checkout forward-issues && git pull --rebase)

@malfet
Copy link
Copy Markdown
Contributor

malfet commented Sep 4, 2025

@pytorchbot merge -i

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

Merge started

Your change will be merged while ignoring the following 1 checks: trunk / linux-jammy-cuda12.8-py3.10-gcc11 / test (default, 2, 5, linux.g6.4xlarge.experimental.nvidia.gpu)

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

@jeanschmidt
Copy link
Copy Markdown
Contributor

@pytorchbot revert -m "checking if revert will fix https://github.com/pytorch/pytorch/actions/runs/17470601839/job/49621447581" -c ignoredsignal

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

@pytorchbot successfully started a revert job. Check the current status here.
Questions? Feedback? Please reach out to the PyTorch DevX Team

@pytorchmergebot
Copy link
Copy Markdown
Collaborator

@lakshayg your PR has been successfully reverted.

pytorchmergebot added a commit that referenced this pull request Sep 4, 2025
@pytorchmergebot pytorchmergebot added Reverted ci-no-td Do not run TD on this PR labels Sep 4, 2025
@lakshayg lakshayg marked this pull request as draft September 5, 2025 19:48
markc-614 pushed a commit to markc-614/pytorch that referenced this pull request Sep 17, 2025
I found a number of places that seem to want forwarding
references but the type signature does not reflect that

Pull Request resolved: pytorch#161094
Approved by: https://github.com/malfet
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
I found a number of places that seem to want forwarding
references but the type signature does not reflect that

Pull Request resolved: pytorch#161094
Approved by: https://github.com/malfet
mansiag05 pushed a commit to mansiag05/pytorch that referenced this pull request Sep 22, 2025
cleonard530 pushed a commit to cleonard530/pytorch that referenced this pull request Sep 22, 2025
I found a number of places that seem to want forwarding
references but the type signature does not reflect that

Pull Request resolved: pytorch#161094
Approved by: https://github.com/malfet
cleonard530 pushed a commit to cleonard530/pytorch that referenced this pull request Sep 22, 2025
dsashidh pushed a commit to dsashidh/pytorch that referenced this pull request Sep 26, 2025
I found a number of places that seem to want forwarding
references but the type signature does not reflect that

Pull Request resolved: pytorch#161094
Approved by: https://github.com/malfet
dsashidh pushed a commit to dsashidh/pytorch that referenced this pull request Sep 26, 2025
@github-actions
Copy link
Copy Markdown
Contributor

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

@github-actions github-actions Bot added the Stale label Nov 27, 2025
@lakshayg lakshayg closed this Dec 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci-no-td Do not run TD on this PR ciflow/trunk Trigger trunk jobs on your pull request Merged module: cpu CPU specific problem (e.g., perf, algorithm) NNC oncall: jit Add this issue/PR to JIT oncall triage queue open source release notes: quantization release notes category Reverted Stale triaged This issue has been looked at a team member, and triaged and prioritized into an appropriate module

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants