vyos-cloud-init.git/cloudinit/signal_handler.py, branch circinus-public-unmaintained (mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=circinus-public-unmaintained 2021-12-16T02:16:38+00:00 Adopt Black and isort (SC-700) (#1157) 2021-12-16T02:16:38+00:00 James Falcon james.falcon@canonical.com 2021-12-16T02:16:38+00:00 urn:sha1:bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf Applied Black and isort, fixed any linting issues, updated tox.ini and CI. cloudinit: replace "from six import X" imports (except in util.py) (#183) 2020-01-31T15:15:31+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-01-31T15:15:31+00:00 urn:sha1:1bb1896ec900622e02c1ffb59db4d3f2df4a964d LICENSE: Allow dual licensing GPL-3 or Apache 2.0 2016-12-22T22:04:28+00:00 Jon Grimm jon.grimm@canonical.com 2016-11-22T23:09:53+00:00 urn:sha1:b2a9f33616c806ae6e052520a8589113308f567c This has been a recurring ask and we had initially just made the change to the cloud-init 2.0 codebase. As the current thinking is we'll just continue to enhance the current codebase, its desirable to relicense to match what we'd intended as part of the 2.0 plan here. - put a brief description of license in LICENSE file - put full license versions in LICENSE-GPLv3 and LICENSE-Apache2.0 - simplify the per-file header to reference LICENSE - tox: ignore H102 (Apache License Header check) Add license header to files that ship. Reformat headers, make sure everything has vi: at end of file. Non-shipping files do not need the copyright header, but at the moment tests/ have it. adjust signal_handler for version changes. 2016-08-05T21:36:54+00:00 Scott Moser smoser@brickies.net 2016-08-05T21:35:33+00:00 urn:sha1:d0b2863bc8dfab2919b11bbcc2584c1c51223028 signal_handler was still using vr.version(). Largely merge lp:~harlowja/cloud-init/py2-3 albeit manually because it seemed 2015-01-21T22:56:53+00:00 Barry Warsaw barry@python.org 2015-01-21T22:56:53+00:00 urn:sha1:f895cb12141281702b34da18f2384deb64c881e7 to be behind trunk. `tox -e py27` passes full test suite. Now to work on replacing mocker. do not disable logging on signal 2012-09-19T20:33:56+00:00 Scott Moser smoser@ubuntu.com 2012-09-19T20:33:56+00:00 urn:sha1:cef4e846797ed7aee29e18b00810887c67591abc I had previously asked for this, but we're hoping to handle it in a more generic way. Just because we receive a signal doesn't mean that all logging is broken. The more general solution we'll chase is to catch a failure of a log message and fall back if necessary across the board. That way cloud-init will still send logging to the right places on a user interupt. change exit messages to include signal name 2012-09-19T20:26:45+00:00 Scott Moser smoser@ubuntu.com 2012-09-19T20:26:45+00:00 urn:sha1:a637b5f74948324173219a2e7817c7f19d864281 Add a basic signal test and write out all 2012-09-14T21:32:31+00:00 Joshua Harlow harlowja@yahoo-inc.com 2012-09-14T21:32:31+00:00 urn:sha1:2899c638c04907461024dff0d32c1cc57ae4b6d4 the signal information in one block instead of many. Fix pylintness. 2012-09-07T01:14:03+00:00 Joshua Harlow harlowja@yahoo-inc.com 2012-09-07T01:14:03+00:00 urn:sha1:0f385445522cf8fe76391c0c0c855b6fa7ad9f50 Add capturing of basic signal handlers to 2012-09-07T01:12:21+00:00 Joshua Harlow harlowja@yahoo-inc.com 2012-09-07T01:12:21+00:00 urn:sha1:01ad8fc5b1928c01367b32022ceab09f1dc5dc26 handle those signals more gracefully and with better messaging than what comes builtin.