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

Graceful shutdown on Ctrl+C in blender/yacat #134

Merged
merged 2 commits into from
Nov 23, 2020

Conversation

azawlocki
Copy link
Contributor

@azawlocki azawlocki commented Nov 23, 2020

Resolves #118
Improves #132

Also resolves some issues reported after the last testing session

  • All asyncio task are cancelled and gathered at the end of Executor.submit() to ensure that no "Exception was never retrieved" errors occur at shutdown

  • KeyboardInterrupt is caught at the end of blender.py/yacat.py to ensure that pressing Ctrl+C for the second time does not print traceback

@azawlocki azawlocki requested a review from filipgolem November 23, 2020 09:24
@@ -119,7 +119,20 @@ async def worker(ctx: WorkContext, tasks):
task = loop.create_task(main(subnet_tag=args.subnet_tag))
try:
loop.run_until_complete(task)
except (Exception, KeyboardInterrupt) as e:
print(e)
except KeyboardInterrupt:
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd put this into some utility function... context manager in examples/utils.py maybe?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good idea, but I would create an issue for this instead of including it in the current PR

Copy link
Contributor

Choose a reason for hiding this comment

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

I prefer the example to fit in one file and be as short as possible. I discussed this with @mfranciszkiewicz last week - Marek, can you share your opinion here?

Copy link
Contributor

@mfranciszkiewicz mfranciszkiewicz Nov 23, 2020

Choose a reason for hiding this comment

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

IMHO utils.py is not the way to go

  • the argument parser is trivial enough to be copied between examples; we're copying the sys.path expansion code instead
  • if there's a need for creating common worker launcher code / logging facility, maybe it's worth considering making those a part of the library

I'm worried that the initial purpose of examples will be obscured and they'll be better off being separate apps instead.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mfranciszkiewicz thanks for your remarks. Including the code for building the parser in blender.py/yacat.py was also my idea at the beginning but then a reviewer convinced me that that code should be shared between the example scripts. That's how we ended up with a shared examples/utils.py module.

I'd consider adding some boilerplate code for creating an asyncio event loop and running the main task + handling graceful termination to the yapapi itself (and maybe pulling the code for creating commandline parser back to b lender.py/yacat.py) but that's not in the scope of the current PR.

@@ -119,7 +119,20 @@ async def worker(ctx: WorkContext, tasks):
task = loop.create_task(main(subnet_tag=args.subnet_tag))
try:
loop.run_until_complete(task)
except (Exception, KeyboardInterrupt) as e:
print(e)
except KeyboardInterrupt:
Copy link
Contributor

Choose a reason for hiding this comment

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

I prefer the example to fit in one file and be as short as possible. I discussed this with @mfranciszkiewicz last week - Marek, can you share your opinion here?

@azawlocki azawlocki merged commit 6fb69fe into b0.4 Nov 23, 2020
@azawlocki azawlocki deleted the hotfix/graceful-shutdown branch November 23, 2020 12:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants