Skip to content

Conversation

@peterbell10
Copy link
Collaborator

@peterbell10 peterbell10 commented Nov 14, 2022

Stack from ghstack (oldest at bottom):

Ref #70924

This addresses part 1 of the issue, allowing torch.squeeze to be
passed a tuple of dimensions. e.g.

x.squeeze(0).squeeze(0)

can now be written

x.squeeze((0, 1))

(assuming x has at least 2 dimensions)

cc @mlazos @soumith @voznesenskym @yanboliang @penguinwu @anijain2305 @EikanWang @jgong5 @Guobing-Chen @chunyuan-w @XiaobingSuper @zhuhaozhe @blzheng @Xia-Weiwen @wenzhe-nrv @jiayisunx @desertfire

Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze(0, 1)
```
(assuming x has at least 2 dimensions)

[ghstack-poisoned]
@pytorch-bot
Copy link

pytorch-bot bot commented Nov 14, 2022

🔗 Helpful Links

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

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

✅ No Failures

As of commit e44436d:
💚 Looks good so far! There are no failures yet. 💚

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

peterbell10 added a commit that referenced this pull request Nov 14, 2022
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze(0, 1)
```
(assuming x has at least 2 dimensions)

ghstack-source-id: 23ef534
Pull Request resolved: #89017
@peterbell10 peterbell10 added release notes: python_frontend python frontend release notes category topic: improvements topic category labels Nov 15, 2022
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze(0, 1)
```
(assuming x has at least 2 dimensions)

[ghstack-poisoned]
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze(0, 1)
```
(assuming x has at least 2 dimensions)

[ghstack-poisoned]
peterbell10 added a commit that referenced this pull request Nov 15, 2022
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze(0, 1)
```
(assuming x has at least 2 dimensions)

ghstack-source-id: 8b633ca
Pull Request resolved: #89017
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze(0, 1)
```
(assuming x has at least 2 dimensions)

[ghstack-poisoned]
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze(0, 1)
```
(assuming x has at least 2 dimensions)

[ghstack-poisoned]
peterbell10 added a commit that referenced this pull request Nov 15, 2022
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze(0, 1)
```
(assuming x has at least 2 dimensions)

ghstack-source-id: e65942c
Pull Request resolved: #89017
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze((0, 1))
```
(assuming x has at least 2 dimensions)

[ghstack-poisoned]
peterbell10 added a commit that referenced this pull request Nov 16, 2022
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze((0, 1))
```
(assuming x has at least 2 dimensions)

ghstack-source-id: c486073
Pull Request resolved: #89017
@peterbell10 peterbell10 marked this pull request as ready for review November 20, 2022 21:30
@albanD
Copy link
Collaborator

albanD commented Nov 22, 2022

@mruberry can you take care of this one?

…dimensions at once"

Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze((0, 1))
```
(assuming x has at least 2 dimensions)

[ghstack-poisoned]
peterbell10 added a commit that referenced this pull request Dec 5, 2022
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze((0, 1))
```
(assuming x has at least 2 dimensions)

ghstack-source-id: 9e7299c
Pull Request resolved: #89017
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze((0, 1))
```
(assuming x has at least 2 dimensions)

[ghstack-poisoned]
…ns at once"

Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze((0, 1))
```
(assuming x has at least 2 dimensions)

cc mlazos soumith voznesenskym yanboliang penguinwu anijain2305 EikanWang jgong5 Guobing-Chen chunyuan-w XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx desertfire

[ghstack-poisoned]
Copy link
Collaborator

@albanD albanD left a comment

Choose a reason for hiding this comment

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

Ok!

@peterbell10 peterbell10 added the ciflow/trunk Trigger trunk jobs on your pull request label Jan 3, 2023
@peterbell10
Copy link
Collaborator Author

@pytorchbot merge -f "ROCm timeout is unrelated"

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

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

@mehtanirav
Copy link
Contributor

This PR is causing internal build failures with errors like

[2023-01-04T23:03:00.073-08:00] Stderr: fbcode/caffe2/aten/src/ATen/native/nested/NestedTensorMath.cpp:711:20: error: comparison of integers of different signs: 'int64_t' (aka 'long') and 'unsigned long' [-Werror,-Wsign-compare]
[CONTEXT] [2023-01-04T23:03:00.073-08:00]   TORCH_CHECK(ndim > 1 + dims.size(),
[CONTEXT] [2023-01-04T23:03:00.073-08:00]               ~~~~ ^ ~~~~~~~~~~~~~~~

@mehtanirav
Copy link
Contributor

@pytorchbot revert -m "Internal breakages" -c ghfirst

@pytorchmergebot
Copy link
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
Collaborator

@peterbell10 your PR has been successfully reverted.

pytorchmergebot added a commit that referenced this pull request Jan 5, 2023
@ngimel
Copy link
Collaborator

ngimel commented Jan 5, 2023

Next PR in the stack will also need to be reverted, why wasn't it reverted automatically?

@mehtanirav
Copy link
Contributor

Next PR in the stack will also need to be reverted, why wasn't it reverted automatically?

Looks like there was no conflict in reverting this PR independently. do we still need to revert #91602?

@ngimel
Copy link
Collaborator

ngimel commented Jan 5, 2023

Yes, even though there's no conflicts, #91602 relies on functionality introduced here. Could we have done a quick fix here instead? If unsigned comparison is the only problem, that's an easy forward fix.

@peterbell10 peterbell10 reopened this Jan 6, 2023
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze((0, 1))
```
(assuming x has at least 2 dimensions)

cc mlazos soumith voznesenskym yanboliang penguinwu anijain2305 EikanWang jgong5 Guobing-Chen chunyuan-w XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx desertfire

[ghstack-poisoned]
Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze((0, 1))
```
(assuming x has at least 2 dimensions)

cc mlazos soumith voznesenskym yanboliang penguinwu anijain2305 EikanWang jgong5 Guobing-Chen chunyuan-w XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx desertfire

[ghstack-poisoned]
…t once"

Ref #70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze((0, 1))
```
(assuming x has at least 2 dimensions)

cc mlazos soumith voznesenskym yanboliang penguinwu anijain2305 EikanWang jgong5 Guobing-Chen chunyuan-w XiaobingSuper zhuhaozhe blzheng Xia-Weiwen wenzhe-nrv jiayisunx desertfire

[ghstack-poisoned]
peterbell10 added a commit to peterbell10/pytorch that referenced this pull request Jan 16, 2023
Ref pytorch#70924

This addresses part 1 of the issue, allowing `torch.squeeze` to be
passed a tuple of dimensions. e.g.
```python
x.squeeze(0).squeeze(0)
```
can now be written
```python
x.squeeze((0, 1))
```
(assuming x has at least 2 dimensions)

ghstack-source-id: c8cb529
Pull Request resolved: pytorch#89017
@peterbell10
Copy link
Collaborator Author

@pytorchbot merge

@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

@facebook-github-bot facebook-github-bot deleted the gh/peterbell10/464/head branch June 8, 2023 18:22
@ScXfjiang ScXfjiang mentioned this pull request Apr 22, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants