The BEAT computation being fully asynchronous, the client does
not expect immediate reply to its requests. Therefor this
warning is misleading.

Unlike the Majordomo ZMQ example, we have "single" workers with work
assigned and possible actions taken on arrival/departure. Therefore
the purge should check the whole list to ensure that everything is
done with respect to the status of the worker.

This implements a new paradigm for the process nodes
communication. Based on the ZMQ Majordomo protocol,
its goal is to improve reliability of the setup.

Add automatic test image pulling if not already available (closes #63)

Closes #63

See merge request !51

Implement loop with input test

See merge request !47

Currently only the status of the main algorithm container
was taken into account to gather the stderr output of all
other containers. This patch changes this so that if
something fails but the main containers ends successfully
the other containers output can still be analysed.

Not all tests were checking for None which might happen
for reason outside of tests error.

These two algorithm allow for better testing of a complete
experiment with a database used for input of both loop and
loop user algorithm.

Temporarily remove framework trove classifier to unblock pypi upload…

See merge request !50

[setup] Temporarily remove framework trove classifier to unblock pypi upload (c.f. issue beat.backend.python#19) [ci skip]

merge new documentation to master

See merge request !48

Samuel GAIST authored Dec 10, 2018 and Zohreh MOSTAANI committed Dec 12, 2018

Update the docker image versions.
Add notice for newer version check.