[Bug]: AutoDeploy: torch-compile: fix fake ops for prepare_metadata and other ops
Open
Nobody has claimed this yet.
bug
Infra
triaged
- Dominant language
- Python
- Stars
- 14.7k
- Forks
- 2.8k
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 489
Description
System Info
Fake ops for our prepare_metadata ops are not correct since the shapes are dependent on the input values of the tensors. This will cause torch-compile to fail.
There is two potential ways we can consider fixing it:
- Hack to see if we can trick the torch-compile shape analysis
- Properly declare additional dynamic shapes that will correctly describe the metadata
This should probably also tie into our discussion of how and if we want to use torch-compile at all moving forward...
Who can help?
No response
Information
- The official example scripts
- My own modified scripts
Tasks
- An officially supported task in the
examplesfolder (such as GLUE/SQuAD, ...) - My own task or dataset (give details below)
Reproduction
n/a
Expected behavior
n/a
actual behavior
n/a
additional notes
n/a
Before submitting a new issue...
- Make sure you already searched for relevant issues, and checked the documentation and examples for answers to frequently asked questions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.