New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ONNX] Fix graph position to insert clone node for inplace op removal (#50123) #51520
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…#50123) Previous insertBefore approach might end-up inserting clone node in inner sub-blocks, while then the node being used later at other outside call sites. [ghstack-poisoned]
This was referenced Feb 2, 2021
facebook-github-bot
added
the
oncall: jit
Add this issue/PR to JIT oncall triage queue
label
Feb 2, 2021
💊 CI failures summary and remediationsAs of commit ee61384 (more details on the Dr. CI page):
1 failure not recognized by patterns:
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. |
This was referenced Feb 2, 2021
This was referenced Feb 2, 2021
Closed
… op removal (#50123)" Previous insertBefore approach might end-up inserting clone node in inner sub-blocks, while then the node being used later at other outside call sites. [ghstack-poisoned]
… op removal (#50123)" Previous insertBefore approach might end-up inserting clone node in inner sub-blocks, while then the node being used later at other outside call sites. Differential Revision: [D26203124](https://our.internmc.facebook.com/intern/diff/D26203124) [ghstack-poisoned]
@SplitInfinity merged this pull request in 3cc4600. |
BowenBao
added a commit
to BowenBao/pytorch
that referenced
this pull request
Feb 5, 2021
…pytorch#50123) Previous insertBefore approach might end-up inserting clone node in inner sub-blocks, while then the node being used later at other outside call sites. ghstack-source-id: e9179a4d525906e0197289e31072f895d289637e Pull Request resolved: pytorch#51520
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stack from ghstack:
Previous insertBefore approach might end-up inserting clone node in inner sub-blocks, while then the node being used later at other outside call sites.
Differential Revision: D26203124