René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Cannot cleanly shut down an asyncio based server","articleBody":"# Bug report\n\n### Bug description:\n\nWhen writing an asyncio based service, you basically have this sequence:\n\n1. Create an event loop\n2. Register a SIGTERM handler\n3. Start your server\n4. `loop.run_forever()`\n5. SIGTERM causes a `loop.stop()`\n6. Close the server\n7. Close event loop\n\nIf there are any connections active at this point, then they don't get discarded until interpreter shutdown, with the result that you get a bunch of ResourceWarnings (and cleanup code might not run).\n\nIt would be very useful if there was a `Server.close_clients()` or something like that. Even a `Server.all_transports()` would be useful, as then you could do something similar as when doing a `Task.cancel()` on what you get from `loop.all_tasks()`.\n\nWe could poke at `Server._transports`, but that is something internal that might change in the future.\n\nThere is `Server.wait_closed()`, but that hangs until all clients have gracefully disconnected. It doesn't help us when we want to shut down the service *now*.\n\n### CPython versions tested on:\n\n3.12\n\n### Operating systems tested on:\n\nLinux\n\n\u003c!-- gh-linked-prs --\u003e\n### Linked PRs\n* gh-113690\n* gh-113713\n* gh-113714\n* gh-114432\n* gh-116632\n* gh-116784\n\u003c!-- /gh-linked-prs --\u003e\n","author":{"url":"https://github.com/CendioOssman","@type":"Person","name":"CendioOssman"},"datePublished":"2023-12-28T10:14:03.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":33},"url":"https://github.com/113538/cpython/issues/113538"}