Bug 12403 - In async services, exception passed to async error callback is assumed to have been thrown
Summary: In async services, exception passed to async error callback is assumed to hav...
Status: RESOLVED FIXED
Alias: None
Product: dbus
Classification: Unclassified
Component: python (show other bugs)
Version: unspecified
Hardware: Other All
: high normal
Assignee: Simon McVittie
QA Contact: John (J5) Palmieri
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-09-12 05:43 UTC by Simon McVittie
Modified: 2007-09-27 11:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
wrap traceback call in try/except block (550 bytes, text/x-patch)
2007-09-12 08:35 UTC, John (J5) Palmieri 		Details
View All

Description Simon McVittie 2007-09-12 05:43:55 UTC 
The implementation of asynchronous services assumes that the exception passed to the error callback was thrown and is still the current exception, and tries to pull out a traceback. This means that this:

async_err_cb(SomeError('oops'))

won't work.
Comment 1 John (J5) Palmieri 2007-09-12 08:35:02 UTC 
Created attachment 11529 [details]
wrap traceback call in try/except block

Seems like this is an easy fix though I guess stringafying the exception may be superfluous,
Comment 2 Simon McVittie 2007-09-27 11:59:50 UTC 
Fixed in 0.82.3 with a different patch.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.