GitLab

Now requires a sequential loop algorithm.

This method will trigger the reading of the input
by the loop algorithm.

Implement loop output

See merge request !54

This makes its usage more clear and explicit.

It also fixes an issue where the loop paradigm can only be
used with a block having a database as input.

This change requires update in beat/beat.core> executors
calling these scripts.

This allows to have the data generated with the correct user id
if provided in the configuration and doesn't match the current
user running the container.

This will allow to reuse the code in beat/beat.core.

Currently input and output cache files were "shared"
because of how the configuration was made.

Also, the input for the loop algorithm, although the same
as the loop_user, was not properly generated as a separate
input.

This reduces code duplication and will also
help clean up beat/beat.core> a bit.

This allows files with similar name not to clash.

For example input and input_data.

If process fails, return early and send done message to
other parties. This allows to stop everything more
cleanly.

Synchronous operation means that the following loop user
write will happen after the loop write method was called.

The end data index parameter allows to keep the output of
both block in sync.

This method will be called on the loop when
an output is written by the loop user algorithm.

This will be used to let the loop know that a
write occurred in the loop_user block.

This reflects more correctly what the test
is about.

Fix loop dataformat export

See merge request !56

This will ensure that exporting algorithm works correctly.