[ONNX] Fix circular padding to support dynamic axes#95647
[ONNX] Fix circular padding to support dynamic axes#95647ilyasher wants to merge 2 commits intopytorch:masterfrom
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/95647
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit f877b1d: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
BowenBao
left a comment
There was a problem hiding this comment.
LGTM, thanks for your contribution! You need to sign EasyCLA for me to merge it.
|
@pytorchbot rebase |
|
@pytorchbot successfully started a rebase job. Check the current status here |
|
Successfully rebased |
39894d2 to
d72682b
Compare
Thanks, I'm trying to get that sorted out right now. |
|
/easycla |
Good thinking, I will complete the CLA with my other email. |
|
/easycla |
|
@pytorchbot rebase |
|
@pytorchbot successfully started a rebase job. Check the current status here |
|
Successfully rebased |
a69e3ea to
5f7806e
Compare
|
The commit shows my email as I will fix the commit with the correct email and force-push |
5f7806e to
fcc854d
Compare
|
/easycla |
1 similar comment
|
/easycla |
|
@pytorchbot rebase |
|
You don't have permissions to rebase this PR since you are a first time contributor. If you think this is a mistake, please contact PyTorch Dev Infra. |
|
@BowenBao I finally got the CLA approved, what else do I need to do to merge this PR? Thanks for all your help. |
|
@pytorchbot rebase |
|
@pytorchbot successfully started a rebase job. Check the current status here |
This commit fixes a bug where the ONNX exporter for circular padding queried the input tensor shape in order to get the correct 'end' index for a slice node. This doesn't work when the axis in question is has dynamic size. The commit fixes this by setting the 'end' index to INT_MAX, which is the recommended way of slicing to the end of a dimension with unknown size per ONNX spec.
Co-authored-by: Bowen Bao <[email protected]>
|
Successfully rebased |
fcc854d to
f877b1d
Compare
|
@pytorchbot merge -g |
Merge startedYour 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 |
Merge failedReason: Not merging any PRs at the moment because there is a merge blocking https://github.com/pytorch/pytorch/labels/ci:%20sev issue open at: Details for Dev Infra teamRaised by workflow job |
|
@pytorchbot merge -g |
Merge startedYour 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 |
This commit fixes a bug where the ONNX exporter for circular padding queried the input tensor shape in order to get the correct 'end' index for a slice node. This doesn't work when the axis in question is has dynamic size. The commit fixes this by setting the 'end' index to INT_MAX, which is the recommended way of slicing to the end of a dimension with unknown size per ONNX spec. See https://onnx.ai/onnx/operators/onnx__Slice.html Also adds a regression test. Pull Request resolved: pytorch/pytorch#95647 Approved by: https://github.com/BowenBao
This commit fixes a bug where the ONNX exporter for circular padding queried the input tensor shape in order to get the correct 'end' index for a slice node. This doesn't work when the axis in question is has dynamic size. The commit fixes this by setting the 'end' index to INT_MAX, which is the recommended way of slicing to the end of a dimension with unknown size per ONNX spec.
See https://onnx.ai/onnx/operators/onnx__Slice.html
Also adds a regression test.