Concurrent Log Handler for Python

stream lock is not closed

Bug #1199332 reported by Dan Callaghan
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Concurrent Log Handler for Python
Status tracked in Trunk
Trunk
Fix Released
High
Lowell Alleman
Unstable
Fix Released
Undecided
Unassigned

Bug Description

The .close() method does not close the stream lock, which can lead to some very annoying side effects, for example:

https://bugzilla.redhat.com/show_bug.cgi?id=952929

I'm using the attached patch in the Fedora package of ConcurrentLogHandler.

Revision history for this message
Dan Callaghan (djc) wrote :
Revision history for this message
Dan Callaghan (djc) wrote :

One more patch is needed for this as well. As of Python 2.7, logging.shutdown calls acquire/release around flush and close so ConcurrentLogHandler can end up trying to release the stream lock after it is already closed.

https://bugzilla.redhat.com/show_bug.cgi?id=905286#c3

Lowell Alleman (lowell-alleman)
Changed in python-concurrent-log-handler:
status: New → In Progress
Lowell Alleman (lowell-alleman)
Changed in python-concurrent-log-handler:
assignee: nobody → Lowell Alleman (lowell-alleman)
importance: Undecided → High
Revision history for this message
Lowell Alleman (lowell-alleman) wrote :

http://bazaar.launchpad.net/~lowell-alleman/python-concurrent-log-handler/master/revision/30

Revision history for this message
Lowell Alleman (lowell-alleman) wrote :

http://bazaar.launchpad.net/~lowell-alleman/python-concurrent-log-handler/0.9/revision/33

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.