[openstack-dev] [taskflow] Begging for reviews

Greg Hill greg.hill at RACKSPACE.COM
Tue Feb 2 16:43:18 UTC 2016

Normally I reserve the begging for IRC, but since the other cores aren't always on, I'm taking the shotgun approach.  If you aren't a core on taskflow, then you can safely skip the rest of this email.

We have a number of open reviews with a single +2 that need another core reviewer to sign off.  Included in that is a blocker for the next release:


That was a bug introduced since the last release with trapping exception arguments from tasks that will affect anyone running the worker-based engine.  The case I ran into was in requests where it did something akin to:

    raise RetryException(ConnectionError())

That inner exception could not be converted to JSON so it threw an exception and aborted the job.

Also, these are important changes (IMO):

Make the worker stop processing queued tasks when it stops:

Similarly for the conductor:

Allow revert methods to have different method signatures from execute and just work:

(depends on https://review.openstack.org/267131 )

Don't revert tasks that were never executed (I'm simplifying):

And more.  I'm just highlighting the ones that most affect me personally, but in general, the review queue is really backlogged.  Any help is appreciated.  Bring it!



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160202/57770316/attachment.html>

More information about the OpenStack-dev mailing list