delta/openstack/taskflow.git/taskflow, branch queens-eol

Fix invalid json unit test

2018-02-18T11:24:00+00:00

Recent versions of oslo.serialization have made it possible to dump
exceptions to JSON, which broke a unit test in taskflow that
assumed exceptions were unserializable.  This change switches to an
explicitly unserializable class for that test.

Change-Id: If6d19bc9fcf1f1813cb087d42dc7ba6a61c71b3d
Closes-Bug: 1748241
(cherry picked from commit 44ce6eae918d44c0ee85998d0526e916dee8de26)

Merge "Avoid log warning when closing is underway (on purpose)"

2017-12-12T22:33:40+00:00

Remove class StopWatch from timing

2017-10-24T05:44:27+00:00

In new release timeutils.StopWatch can be used from oslo.uitls, so it was deprecated for removal in
timing.py

Change-Id: I138b8d276998a4ea2537966767cbd14f96daf757
Closes-Bug: #1715043

Merge "Remove method blather in log adapter"

2017-10-24T03:17:54+00:00

Remove method blather in log adapter

2017-09-04T06:06:56+00:00

As method blather was using in new place, it was deprecated for removal
in new release.

Change-Id: Ic8d425e1774d6b7090ec105f2b37467a90c6e1e6
Closes-Bug: #1714873

Remove kwarg timeout in executor conductor

2017-09-01T12:27:58+00:00

The method stop returns immediately regardless of whether the conductor has been
stopped, so kwarg timeout is no longer necessary, and it is deprecated for removal.

Change-Id: I50e5cbb1a00eb9b6f358f150716d2a5d682a49c9

Avoid log warning when closing is underway (on purpose)

2017-08-01T11:28:26+00:00

Related-Bug: #1557107

Change-Id: I8b2f327dadbf038cd050f05fbc46a428282a3d82

Update URLs in documents according to document migration

2017-07-13T04:05:18+00:00

Change-Id: I9ca92fdcec388e02462332e04fe7c1bf8b5f64b8

Merge "Fix process based executor task proxying-back events"

2017-07-11T10:48:25+00:00

Fix process based executor task proxying-back events

2017-07-11T03:14:04+00:00

Let's dive into what the problem is here.

First a description of what happens to a task that
is to be executed in a external (but local) process
via the process executor mechanism.

When a task is about to be sent to execute in the
external (but local) process its first cloned, this
is mainly done so that its notification callbacks can
be altered in a safe manner (ie not altering the
original task object to do this) and that clone has
its notifier emptied out.

What replaces the clone's notifier callbacks though
is a new object (that has a __call__ method so it
looks like just another callback) that will send
messages to the parent process (the one that has
the engine in it) over a secure(ish) channel whenever
the local task triggers its notifier notify() method.

This allows for callbacks in the parent process to
get triggered because once the messages recieved the
original tasks notifier object has its notify() method
called (therefore those callbacks do not really know
the task they are getting messages from is executing out
of process).

The issue though is that if the ANY(*) event type is registered
due to how it works in the notifier is that if the child/cloned
notifier has the ANY event type registered and the cloned task
calls notify() with a specific event this will cause the ANY
callback (in the clone) to transmit a message *and* it will
cause the *specific* event callback to also transmit a message
back to the parent process.

On the engine process side it will get 2 messages and trigger
the callbacks 3 times (twice for the specific event callback
because how the local notifier has the ANY callback registered
and one more time when the local process also sends the same
event based on its registration of the ANY event in the child
process).

This is not what is expected (the message rcved on the engine
process should only trigger one callback to get triggered
if the engine process task has no ANY callback registered or two
engine process callbacks to get triggered if the engine process
task has the ANY callback registered).

Closes-Bug: #1537948

Change-Id: I271bf1f23ad73df6c177cf00fd902c4881ba44ae