-
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
Removed flush_logs_every_n_steps
argument from Trainer
#13074
Merged
carmocca
merged 6 commits into
Lightning-AI:master
from
shenoynikhil:flush-logs-every-n-steps
May 25, 2022
Merged
Removed flush_logs_every_n_steps
argument from Trainer
#13074
carmocca
merged 6 commits into
Lightning-AI:master
from
shenoynikhil:flush-logs-every-n-steps
May 25, 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
shenoynikhil
commented
May 14, 2022
pytorch_lightning/trainer/connectors/logger_connector/logger_connector.py
Show resolved
Hide resolved
shenoynikhil
commented
May 14, 2022
shenoynikhil
changed the title
[WIP] Removed
Removed May 14, 2022
flush_logs_every_n_steps
argument from Trainerflush_logs_every_n_steps
argument from Trainer
awaelchli
approved these changes
May 14, 2022
pytorch_lightning/trainer/connectors/logger_connector/logger_connector.py
Show resolved
Hide resolved
shenoynikhil
requested review from
williamFalcon,
tchaton,
carmocca,
justusschock,
edenlightning,
Borda,
SeanNaren,
kaushikb11 and
rohitgr7
as code owners
May 14, 2022 19:35
akihironitta
added
breaking change
Includes a breaking change
trainer: argument
community
This PR is from the community
labels
May 16, 2022
44 tasks
carmocca
approved these changes
May 18, 2022
Co-authored-by: Carlos Mocholí <[email protected]>
awaelchli
approved these changes
May 22, 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.
nice, just a minor merge conflict to address!
mergify
bot
added
ready
PRs ready to be merged
and removed
ready
PRs ready to be merged
labels
May 24, 2022
@awaelchli Merged with master to fix the merge conflict |
akihironitta
approved these changes
May 24, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking change
Includes a breaking change
community
This PR is from the community
ready
PRs ready to be merged
trainer: argument
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?
Part of #12521
This PR removes the
flush_logs_every_n_steps
argument in the Trainer Class and the corresponding changes. Made the following edits,docs/source/common/trainer.rst
anddocs/source/visualize/logging_advanced.rst
should_flush
condition inpytorch_lightning/loops/epoch/training_epoch_loop.py
flush_logs_every_n_steps
attribute fromtrainer
inpytorch_lightning/trainer/connectors/logger_connector/logger_connector.py
resolves #9366
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 🙃