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

[Doc] on_startup & on_shutdown signals example with aiopg engine #2196

Merged
merged 3 commits into from
Aug 15, 2017
Merged

[Doc] on_startup & on_shutdown signals example with aiopg engine #2196

merged 3 commits into from
Aug 15, 2017

Conversation

panagiks
Copy link
Contributor

@panagiks panagiks commented Aug 13, 2017

What do these changes do?

Add a documentation example usage of on_startup and on_shutdown signals by properly creating and disposing an aiopg connection engine.

Are there changes in behavior for the user?

No, just documentation.

Related issue number

Relates to #2131.

Checklist

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • If you provide code modification, please add yourself to CONTRIBUTORS.txt
    • The format is <Name> <Surname>.
    • Please keep alphabetical order, the file is sorted by names.
  • Add a new news fragment into the changes folder
    • name it <issue_id>.<type> for example (588.bug)
    • if you don't have an issue_id change it to the pr id after creating the pr
    • ensure type is one of the following:
      • .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.
    • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

@panagiks
Copy link
Contributor Author

If you want me to add another example for redis just drop me a line and I'll add it in Wednesday.

@codecov-io
Copy link

codecov-io commented Aug 13, 2017

Codecov Report

Merging #2196 into 2.2 will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##              2.2    #2196   +/-   ##
=======================================
  Coverage   97.06%   97.06%           
=======================================
  Files          38       38           
  Lines        7691     7691           
  Branches     1341     1341           
=======================================
  Hits         7465     7465           
  Misses        102      102           
  Partials      124      124

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cc2a522...8124335. Read the comment docs.

Copy link
Member

@asvetlov asvetlov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good but on_cleanup signal should be used for db shutdown.
on_shutdown is for graceful closing opened HTTP connections, e.g. closing web sockets and HTTP streaming responses, db connections most likely should be opened at this stage.
on_cleanup is for final cleanup, no web handlers are running at the moment of signal call.

@panagiks
Copy link
Contributor Author

Should be good now :)

@asvetlov asvetlov merged commit 6d27412 into aio-libs:2.2 Aug 15, 2017
@asvetlov
Copy link
Member

Thanks!

@lock
Copy link

lock bot commented Oct 28, 2019

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.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 28, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants