-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Fix number of references to LightningModule #12897
Merged
Merged
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
otaj
requested review from
Borda,
SeanNaren,
carmocca,
justusschock,
kaushikb11 and
rohitgr7
as code owners
April 27, 2022 09:19
rohitgr7
approved these changes
Apr 27, 2022
Co-authored-by: Rohit Gupta <[email protected]>
carmocca
approved these changes
Apr 27, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's wait until PyTorch devs approve the change upstream to merge
Co-authored-by: Rohit Gupta <[email protected]>
carmocca
reviewed
Apr 27, 2022
Co-authored-by: Carlos Mocholí <[email protected]>
Borda
approved these changes
May 4, 2022
mergify
bot
added
ready
PRs ready to be merged
has conflicts
and removed
has conflicts
ready
PRs ready to be merged
labels
May 10, 2022
mergify
bot
added
ready
PRs ready to be merged
and removed
has conflicts
ready
PRs ready to be merged
labels
May 12, 2022
carmocca
approved these changes
May 12, 2022
carmocca
approved these changes
May 13, 2022
awaelchli
approved these changes
May 13, 2022
carmocca
added a commit
that referenced
this pull request
May 13, 2022
Co-authored-by: Rohit Gupta <[email protected]> Co-authored-by: Carlos Mocholí <[email protected]>
ashleve
pushed a commit
to ashleve/pytorch-lightning
that referenced
this pull request
May 13, 2022
Co-authored-by: Rohit Gupta <[email protected]> Co-authored-by: Carlos Mocholí <[email protected]>
ashleve
added a commit
to ashleve/pytorch-lightning
that referenced
this pull request
May 14, 2022
…)" This reverts commit 6a1726a.
carmocca
added a commit
that referenced
this pull request
May 31, 2022
Co-authored-by: Rohit Gupta <[email protected]> Co-authored-by: Carlos Mocholí <[email protected]>
lexierule
pushed a commit
that referenced
this pull request
Jun 1, 2022
Co-authored-by: Rohit Gupta <[email protected]> Co-authored-by: Carlos Mocholí <[email protected]>
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.
What does this PR do?
I know, this looks way too hacky, the proposal in bug report proposes to deal with it in
__del__
method. Problem is, the__del__
method will never be called, exactly because of this issue, because there will always be an internal reference to self. There will be accompanying PR to pytorch to fix it on their sideFixes #12622
Does your PR introduce any breaking changes? If yes, please list them.
Before submitting
PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:
Did you have fun?
Make sure you had fun coding 🙃
cc @otaj @Borda @carmocca @justusschock @awaelchli @ananthsub @ninginthecloud @jjenniferdai @rohitgr7