-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Maintain cleanup context and startup insertion order (#3191) #3194
Maintain cleanup context and startup insertion order (#3191) #3194
Conversation
I found an other way to have the same behavior, I add callback to on_startup and on_cleanup at each cleanup_ctx.append. The callback added to on_cleanup is enable only if on_startup is executed. I will push a new MR version tomorrow. |
Please go ahead |
Codecov Report
@@ Coverage Diff @@
## master #3194 +/- ##
=========================================
Coverage ? 97.97%
=========================================
Files ? 44
Lines ? 8068
Branches ? 1356
=========================================
Hits ? 7905
Misses ? 68
Partials ? 95
Continue to review full report at Codecov.
|
Thanks! |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a [new issue] for related bugs. |
What do these changes do?
We can mix app.cleanup_ctx and app.on_startup the order is preserved.
Are there changes in behavior for the user?
When the startup signal is sent, the handlers added to the
on_startup
list before thecleanup_ctx
willbe executed firstly.
Related issue number
#3191
Checklist
CONTRIBUTORS.txt
CHANGES
folder<issue_id>.<type>
for example (588.bugfix)issue_id
change it to the pr id after creating the pr.feature
: Signifying a new feature..bugfix
: Signifying a bug fix..doc
: Signifying a documentation improvement..removal
: Signifying a deprecation or removal of public API..misc
: A ticket has been closed, but it is not of interest to users.