-
-
Notifications
You must be signed in to change notification settings - Fork 634
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
Allow to terminate an epoch without firing Events.EPOCH_COMPLETED
#3313
Conversation
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.
Thanks a lot for the PR @bonassifabio !
I left a comment, otherwise it looks good to me
Thanks @vfdev-5 for the positive feedback! I still want to include some additional test to make sure handlers are working as expected when |
…ion". - Merged flags "should_terminate_single_epoch" and "_skip_epoch_completed_after_termination".
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.
Thanks for the update, @bonassifabio !
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.
Few nits, otherwise, it looks good to me!
Thanks a lot for working on this feature!
This pull request addresses #3312
Description
Engine.terminate_epoch()
can now be called with the flagskip_epoch_completed=True
, which allows to preventEvents.EPOCH_COMPLETED
to be fired after the termination of the epoch.TODOs
skip_epoch_completed=True
.Other minor changes
skip_completed_after_termination
introduced in Give the option to terminate the engine without firing Events.COMPLET… #3309 has been made renamed to_skip_completed_after_termination
to make it private, for consistency with adb2a01