delta/openstack/taskflow.git/taskflow/utils/lock_utils.py, branch 0.7.1

Let the multi-lock convert the provided value to a tuple

2015-02-11T06:57:24+00:00

Instead of forcing the locks (list or tuple) into a list
and then having the multi-lock code force that back into
a tuple just pass the value through to the multi-lock
class and let it handle the conversion in a more easy to
understand manner (and one that doesn't involve as many
copies).

Change-Id: Ib0e78bacb80aea73af465a91cb4f509904f47990

Merge "Default to using a thread-safe storage unit"

2015-02-07T19:11:21+00:00

Default to using a thread-safe storage unit

2015-02-06T07:19:08+00:00

Instead of having a nominally useful single-threaded storage
unit that uses a dummy r/w lock and a multi-threaded storage
unit just have the storage unit by default protect itself from
multi-threading calls being used on it (with the appropriate
reader/writer locks being activated to make this work
correctly).

Change-Id: Ib6879edb465156a8e54fd5b4002550d1cec49137

Use a thread-identifier that can't easily be recycled

2015-02-05T06:30:59+00:00

Since it is possible for a thread-id from get_ident() to
potentially be recycled at some point in the future it is
safer to use a object that will only be recycled when there
are no more references to it (including the references held
in the reader-writer lock internals).

This avoids any type of thread-identifier recycling issues
that could be possible since it is now assured that said
recycling will not happen until the reader-writer lock itself
is cleaned up by the garbage collector.

Change-Id: I2ea693fe8fc129943648edef8ed6c3596772ebc0

Get event/notification sending working correctly

2014-12-21T03:48:44+00:00

In order to support tasks notifications and progress
updates we need to establish a channel & proxy by which
those events can be sent from the process executing and
producing those events and the originating process that
requested that task to be executed.

This review adds on such a proxy and adjusts a cloned tasks
notification callbacks to place messages on a queue that will
be picked up by a thread in the originating process for dispatch
to the original callbacks that were registered with the non-cloned
task (therefore making the original callbacks appear to be called
as they are supposed to be).

Part of blueprint process-executor

Change-Id: I01c83f13186e4be9fa28c32e34e907bb133e8fb3

Add and use a new simple helper logging module

2014-12-09T06:09:13+00:00

Add a new logging BLATHER level to easily allow its
usage for messages that are below the normal DEBUG level
such as compilation information and scope lookup info
which can be very verbose in logs if always enabled.

Change-Id: I828211403bd02bfd6777b10cdcfe58fb0637a52c

Merge "Link a few of the classes to implemented features/bugs in python"

2014-10-18T19:38:08+00:00

Merge "Remove no longer needed r/w lock interface base class"

2014-10-18T19:27:42+00:00

Fix multilock concurrency when shared by > 1 threads

2014-09-23T18:16:26+00:00

Instead of raising thread errors when another thread
has locks that the consuming thread wants to use just
block and wait and release the correct locks on release
to match the expected vs observed behavior.

This makes it so that a single multilock object can be
shared by many threads and each thread using the object
will correctly obtain and release as expected...

Fixes bug 1371814

Change-Id: Ia21a05fe9249fa019a09c4f30beeb0770ded5150

Remove no longer needed r/w lock interface base class

2014-09-20T05:32:11+00:00

This interface/class was put in place when this code was being
more actively developed to ensure that both the dummy and the
actual class had the same methods, since these two classes
have apis that are now stable we no longer need to have a base
class to enforce the implemented api that itself provides no
added functionality.

Change-Id: Ida4f86b308941ff708db5395a1d266c0c4b75815