Skip to content

Also propagate storage_access_should_throw_ when copying tensor metadata#53816

Closed
ezyang wants to merge 8 commits intogh/ezyang/942/basefrom
gh/ezyang/942/head
Closed

Also propagate storage_access_should_throw_ when copying tensor metadata#53816
ezyang wants to merge 8 commits intogh/ezyang/942/basefrom
gh/ezyang/942/head

Conversation

@ezyang
Copy link
Copy Markdown
Contributor

@ezyang ezyang commented Mar 11, 2021

Stack from ghstack:

Signed-off-by: Edward Z. Yang ezyang@fb.com

Differential Revision: D27036574

Signed-off-by: Edward Z. Yang <ezyang@fb.com>

[ghstack-poisoned]
@facebook-github-bot
Copy link
Copy Markdown
Contributor

facebook-github-bot commented Mar 11, 2021

💊 CI failures summary and remediations

As of commit eac9020 (more details on the Dr. CI page):


💚 💚 Looks good so far! There are no failures yet. 💚 💚


This comment was automatically generated by Dr. CI (expand for details).Follow this link to opt-out of these comments for your Pull Requests.

Please report bugs/suggestions to the (internal) Dr. CI Users group.

@ezyang ezyang requested review from ailzhang and swolchok March 11, 2021 16:05
…ensor metadata"

Signed-off-by: Edward Z. Yang <ezyang@fb.com>

[ghstack-poisoned]
@swolchok
Copy link
Copy Markdown
Contributor

What if you copy_tensor_metadata from a TensorImpl whose storage access should throw(say, a SparseTensorImpl) into one where it shouldn't (say, regular old TensorImpl)? The TensorImpl public interface permits this.

@ezyang
Copy link
Copy Markdown
Contributor Author

ezyang commented Mar 12, 2021

@swolchok I suspect there's an implicit contract saying that the subclass has to be the same in the source and the destination. Would have to add an assert to this effect to check though. FWIW copying sparse tensor's metadata into a dense tensor is pretty bonkers and not something you ever actually want to do.

…ensor metadata"

Signed-off-by: Edward Z. Yang <ezyang@fb.com>

[ghstack-poisoned]
ezyang added 2 commits March 14, 2021 08:30
…ensor metadata"

Signed-off-by: Edward Z. Yang <ezyang@fb.com>

Differential Revision: [D27036574](https://our.internmc.facebook.com/intern/diff/D27036574)

[ghstack-poisoned]
…ensor metadata"

Signed-off-by: Edward Z. Yang <ezyang@fb.com>

Differential Revision: [D27036574](https://our.internmc.facebook.com/intern/diff/D27036574)

[ghstack-poisoned]
@ezyang ezyang requested review from albanD and bhosmer March 15, 2021 15:45
…ensor metadata"

Signed-off-by: Edward Z. Yang <ezyang@fb.com>

Differential Revision: [D27036574](https://our.internmc.facebook.com/intern/diff/D27036574)

[ghstack-poisoned]
ezyang added 2 commits March 15, 2021 11:23
…ensor metadata"

Signed-off-by: Edward Z. Yang <ezyang@fb.com>

Differential Revision: [D27036574](https://our.internmc.facebook.com/intern/diff/D27036574)

[ghstack-poisoned]
…ensor metadata"

Signed-off-by: Edward Z. Yang <ezyang@fb.com>

Differential Revision: [D27036574](https://our.internmc.facebook.com/intern/diff/D27036574)

[ghstack-poisoned]
Copy link
Copy Markdown
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.

lgtm

@facebook-github-bot
Copy link
Copy Markdown
Contributor

@ezyang merged this pull request in 3c45704.

@facebook-github-bot facebook-github-bot deleted the gh/ezyang/942/head branch March 20, 2021 14:15
laurentdupin pushed a commit to laurentdupin/pytorch that referenced this pull request Apr 24, 2026
…ata (pytorch#53816)

Summary:
Pull Request resolved: pytorch#53816

Signed-off-by: Edward Z. Yang <ezyang@fb.com>

Test Plan: Imported from OSS

Reviewed By: mruberry

Differential Revision: D27036574

Pulled By: ezyang

fbshipit-source-id: 71e61b0aa3d46159c9af1112c262cbfa7eaa1879
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants