GitLab

Let's match cw-celerytask-helpers version.

This time no upper range.

This allows installation of cw-celerytask-helpers 0.8.0 which is still
compatible.

Why upgrading CubicWeb minimum version? We don't support 3.25 and
less, and even 3.26 should disappear but it is the last version
that supports Python 2 and it is in consequence sadly still used.
So it is better not to create illusion and be clear that we won't
add a fix for a too old version of CubicWeb. Projects must
upgrade, maintaining very old stuff is dirty work.

In a client project, we add the case of `result.info` being
`UException` (from `cubicweb_nemo.utils`). It resulted in a
problem, because `result.info` is `True` as boolean, but it has
no key, so it crashed. This patch does not resolve the real
problem of having a clean `info` member or knowing why it could
normally have a different type, but at least it eliminates a
problem for the final users.

Using https://six.readthedocs.io/#six.ensure_text

It can occur, for instance in case of "worker lost", that task events are not
sent in the "MONITOR_KEY" list in redis.
The proposed solution is to regularly check pending tasks status.
Since this is almost the same use, this can replace the old "requeue" behavior
of failed sync_task_state() which was based on a "PENDING_KEY" list in redis.

So, every 10 min, was 1min before, but 10 min seems more reasonable, check all
pending tasks status within the visibility_timeout, since tasks outside this
range cannot have state stored in the broker.

In case of exited worker (segfault), AsyncResult.traceback is None and
information is in AsyncResult.result, record it in the failed transition
comment.

Add a dedicated test class, this require to run the worker in prefork mode,
otherwise, in solo mode the information about worker lost isn't tracked.
Use "import ctypes; ctypes.string_at(0)" to simulate a segfault.