BIND 10 #3003: datasrc_config_plugin.py crashes due to uncaught exception without datasrc.spec
BIND 10 Development
do-not-reply at isc.org
Fri Jun 14 07:02:43 UTC 2013
#3003: datasrc_config_plugin.py crashes due to uncaught exception without
datasrc.spec
-------------------------------------+-------------------------------------
Reporter: jinmei | Owner:
Type: defect | Status: new
Priority: medium | Milestone: New
Component: | Tasks
configuration | Resolution:
Keywords: | CVSS Scoring:
Sensitive: 0 | Defect Severity: N/A
Sub-Project: DNS | Feature Depending on Ticket:
Estimated Difficulty: 0 | Add Hours to Ticket: 0
Total Hours: 0 | Internal?: 0
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:1 vorner]:
> Aren't we going to an extreme here already? I mean, we probably don't
want to „recover“ from stuff like missing one of the python library files
or .so files for C++ applications. In which way is this different?
>
> Wouldn't it be better to have some generic way to catch the traces, turn
them into some reasonable log messages, or so? Have a catch-all at the
top-level python program, store the backtrace somewhere and put a fatal
error into log?
That can be a solution. My point is not to leak the exception up to
the interpreter level this way. There may even be a case where we
allow that - missing a critical python module on import, probably
because of installation error, could be one such case. But I don't
think it applies to this case. IMO it should be at least caught at
the top level, and may even have to not be considered fatal.
--
Ticket URL: <http://bind10.isc.org/ticket/3003#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list