-
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
Refactor codebase to use trainer.loggers
over trainer.logger
when needed
#11920
Merged
ananthsub
merged 25 commits into
Lightning-AI:master
from
akashkw:refactor/switch-to-loggers-property
Feb 26, 2022
Merged
Refactor codebase to use trainer.loggers
over trainer.logger
when needed
#11920
ananthsub
merged 25 commits into
Lightning-AI:master
from
akashkw:refactor/switch-to-loggers-property
Feb 26, 2022
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
akashkw
force-pushed
the
refactor/switch-to-loggers-property
branch
from
February 15, 2022 00:13
1a89b4b
to
6cda5b5
Compare
ananthsub
reviewed
Feb 15, 2022
akashkw
force-pushed
the
refactor/switch-to-loggers-property
branch
from
February 15, 2022 19:44
5e223d7
to
44b2fb4
Compare
akashkw
commented
Feb 15, 2022
akashkw
commented
Feb 15, 2022
akashkw
requested review from
williamFalcon,
tchaton,
awaelchli,
carmocca,
SkafteNicki,
Borda,
SeanNaren,
justusschock,
kaushikb11 and
rohitgr7
as code owners
February 15, 2022 20:49
akashkw
force-pushed
the
refactor/switch-to-loggers-property
branch
from
February 15, 2022 23:28
2db1cab
to
649260d
Compare
carmocca
reviewed
Feb 16, 2022
daniellepintz
approved these changes
Feb 24, 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.
LGTM!
rohitgr7
reviewed
Feb 24, 2022
This reverts commit bdd1757.
Can we put back the revert early if no loggers change, since that doesnt seem like it caused the failures? |
akashkw
force-pushed
the
refactor/switch-to-loggers-property
branch
from
February 25, 2022 21:55
c0f411b
to
c277c90
Compare
rohitgr7
approved these changes
Feb 25, 2022
ananthsub
approved these changes
Feb 25, 2022
akashkw
force-pushed
the
refactor/switch-to-loggers-property
branch
from
February 25, 2022 22:40
245f68a
to
961faef
Compare
akashkw
commented
Feb 25, 2022
This was referenced Mar 2, 2022
facebook-github-bot
pushed a commit
to facebookresearch/d2go
that referenced
this pull request
Mar 4, 2022
… needed (#11920) Summary: ### New commit log messages - [7e2f9fbad Refactor codebase to use `trainer.loggers` over `trainer.logger` when needed (#11920)](Lightning-AI/pytorch-lightning#11920) Reviewed By: edward-io Differential Revision: D34583686 fbshipit-source-id: 98e557b761555c24ff296fff3ec6881d141fa777
12 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Refactors codebase to not use
trainer.logger
andLoggerCollection
wherever multiple loggers may appear. Instead usetrainer.loggers
.Part of #11232
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 Review guidelines. In short, see the following bullet-list:
Did you have fun?
Make sure you had fun coding 🙃