From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: pym/portage/util/_eventloop/
Date: Wed, 27 Jun 2018 03:05:57 +0000 (UTC) [thread overview]
Message-ID: <1530068678.6b50ba69f5a8e311fcddfb2e5c203631bd292c71.zmedico@gentoo> (raw)
commit: 6b50ba69f5a8e311fcddfb2e5c203631bd292c71
Author: Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Thu Jun 21 21:03:38 2018 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Wed Jun 27 03:04:38 2018 +0000
URL: https://gitweb.gentoo.org/proj/portage.git/commit/?id=6b50ba69
AsyncioEventLoop: exit after unhandled exception (bug 658684)
Fix portage commands to exit immediately for any unhandled
exceptions that are raised while the asyncio event loop is running
without a tty. If we have a tty then start the debugger,
since in might aid in diagnosis of the problem.
In order to avoid potential interference with API consumers, do not
call set_exception_handler unless portage._internal_caller is True.
Bug: https://bugs.gentoo.org/658684
pym/portage/util/_eventloop/asyncio_event_loop.py | 31 +++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/pym/portage/util/_eventloop/asyncio_event_loop.py b/pym/portage/util/_eventloop/asyncio_event_loop.py
index c07b71103..ea0e03b23 100644
--- a/pym/portage/util/_eventloop/asyncio_event_loop.py
+++ b/pym/portage/util/_eventloop/asyncio_event_loop.py
@@ -2,7 +2,9 @@
# Distributed under the terms of the GNU General Public License v2
import os
+import pdb
import signal
+import sys
try:
import asyncio as _real_asyncio
@@ -53,6 +55,35 @@ class AsyncioEventLoop(_AbstractEventLoop):
self.get_debug = loop.get_debug
self._wakeup_fd = -1
+ if portage._internal_caller:
+ loop.set_exception_handler(self._internal_caller_exception_handler)
+
+ @staticmethod
+ def _internal_caller_exception_handler(loop, context):
+ """
+ An exception handler which drops to a pdb shell if std* streams
+ refer to a tty, and otherwise kills the process with SIGTERM.
+
+ In order to avoid potential interference with API consumers, this
+ implementation is only used when portage._internal_caller is True.
+ """
+ loop.default_exception_handler(context)
+ if 'exception' in context:
+ # If we have a tty then start the debugger, since in might
+ # aid in diagnosis of the problem. If there's no tty, then
+ # exit immediately.
+ if all(s.isatty() for s in (sys.stdout, sys.stderr, sys.stdin)):
+ pdb.set_trace()
+ else:
+ # Normally emerge will wait for all coroutines to complete
+ # after SIGTERM has been received. However, an unhandled
+ # exception will prevent the interrupted coroutine from
+ # completing, therefore use the default SIGTERM handler
+ # in order to ensure that emerge exits immediately (though
+ # uncleanly).
+ signal.signal(signal.SIGTERM, signal.SIG_DFL)
+ os.kill(os.getpid(), signal.SIGTERM)
+
def _create_future(self):
"""
Provide AbstractEventLoop.create_future() for python3.4.
next reply other threads:[~2018-06-27 3:06 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 3:05 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-18 3:41 [gentoo-commits] proj/portage:master commit in: pym/portage/util/_eventloop/ Zac Medico
2018-07-17 19:27 Zac Medico
2018-07-17 19:07 Zac Medico
2018-05-26 20:22 Zac Medico
2018-05-25 3:15 Zac Medico
2018-05-13 16:58 Zac Medico
2018-05-07 0:27 Zac Medico
2018-04-19 6:41 Zac Medico
2018-04-19 6:16 Zac Medico
2018-04-18 21:52 Zac Medico
2018-04-17 18:24 Zac Medico
2018-04-17 18:02 Zac Medico
2018-04-17 6:24 Zac Medico
2018-04-17 0:53 Zac Medico
2018-04-16 8:48 Zac Medico
2018-04-16 6:43 Zac Medico
2018-04-16 0:03 Zac Medico
2018-04-15 22:32 Zac Medico
2018-04-09 1:27 Zac Medico
2018-04-08 22:08 Zac Medico
2018-04-08 21:37 Zac Medico
2018-04-08 21:18 Zac Medico
2018-04-07 20:20 Zac Medico
2017-05-05 18:47 Zac Medico
2013-02-25 23:53 Zac Medico
2013-01-04 3:39 Zac Medico
2012-12-31 3:16 Zac Medico
2012-12-28 1:44 Zac Medico
2012-12-28 1:36 Zac Medico
2012-12-27 2:39 Zac Medico
2012-12-27 2:31 Zac Medico
2012-11-22 12:23 Zac Medico
2012-09-26 2:26 Zac Medico
2012-08-22 16:23 Zac Medico
2012-08-22 5:39 Zac Medico
2012-02-18 4:04 Zac Medico
2012-02-17 23:23 Zac Medico
2012-02-17 22:17 Zac Medico
2012-02-17 10:31 Zac Medico
2012-02-17 10:20 Zac Medico
2012-02-17 9:29 Zac Medico
2012-02-17 6:29 Zac Medico
2012-02-17 6:04 Zac Medico
2012-02-17 3:08 Zac Medico
2012-02-16 21:43 Zac Medico
2012-02-16 21:35 Zac Medico
2012-02-16 4:58 Zac Medico
2012-02-16 4:41 Zac Medico
2012-02-14 16:27 Zac Medico
2012-02-14 3:06 Zac Medico
2012-02-14 1:23 Zac Medico
2012-02-11 23:56 Zac Medico
2012-02-11 21:41 Zac Medico
2012-02-11 21:11 Zac Medico
2012-02-11 19:35 Zac Medico
2012-02-11 2:59 Zac Medico
2012-02-10 0:42 Zac Medico
2012-02-10 0:20 Zac Medico
2012-02-10 0:17 Zac Medico
2012-02-09 7:25 Zac Medico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1530068678.6b50ba69f5a8e311fcddfb2e5c203631bd292c71.zmedico@gentoo \
--to=zmedico@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox