Skip to content
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

Add email callback on train complete #20162

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

loucaspapalazarou
Copy link

@loucaspapalazarou loucaspapalazarou commented Aug 4, 2024

What does this PR do?

This PR adds a new callback that allows a user to notify a list of emails when the training is done. It currently only supports the Google SMTP and is recommended to use an app password. Adding more providers is trivial. If the feedback is positive, I will go ahead and add the docs update as well as proper tests.

Resolves #20133

Before submitting
  • Was this discussed/agreed via a GitHub issue? (not for typos and docs)
  • Did you read the contributor guideline, Pull Request section?
  • Did you make sure your PR does only one thing, instead of bundling different changes together?
  • Did you make sure to update the documentation with your changes? (if necessary)
  • Did you write any new necessary tests? (not for typos and docs)
  • Did you verify new and existing tests pass locally with your changes?
  • Did you list all the breaking changes introduced by this pull request?
  • Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

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:

Reviewer checklist
  • Is this pull request ready for review? (if not, please submit in draft mode)
  • Check that all items from Before submitting are resolved
  • Make sure the title is self-explanatory and the description concisely explains the PR
  • Add labels and milestones (and optionally projects) to the PR so it can be classified

📚 Documentation preview 📚: https://pytorch-lightning--20162.org.readthedocs.build/en/20162/

@github-actions github-actions bot added the pl Generic label for PyTorch Lightning package label Aug 4, 2024
Copy link

codecov bot commented Sep 30, 2024

Codecov Report

Attention: Patch coverage is 37.73585% with 33 lines in your changes missing coverage. Please review.

Project coverage is 81%. Comparing base (474bdd0) to head (45139a1).
Report is 1 commits behind head on master.

❗ There is a different number of reports uploaded between BASE (474bdd0) and HEAD (45139a1). Click for more details.

HEAD has 87 uploads less than BASE
Flag BASE (474bdd0) HEAD (45139a1)
cpu 41 21
python3.10 12 6
lightning_fabric 7 0
pytest 25 2
lightning 31 16
python3.9 11 6
gpu 4 2
python3.11 12 6
python3.12 6 3
Additional details and impacted files
@@            Coverage Diff            @@
##           master   #20162     +/-   ##
=========================================
- Coverage      89%      81%     -8%     
=========================================
  Files         267      265      -2     
  Lines       23064    23062      -2     
=========================================
- Hits        20573    18626   -1947     
- Misses       2491     4436   +1945     

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pl Generic label for PyTorch Lightning package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Email Callback on training done
2 participants