GitLab

The default multiprocess instanciation has
changed from fork to spawn on macOS which
triggers different behaviour.

While they are optional, beat/beat.editor> ensures that
you do not get useless empty fields that may look
like something is missing hence remove them from
here to ensure testing goes well.

These were generated wrongly by the previous
version of the migration helper scripts.

It has also shown that the large database was
wrongly written. This has been changed as well.

Samuel GAIST authored Jan 28, 2021 and Samuel GAIST committed Jan 28, 2021

The wrong name was used to generate the template.

Also improve handling of protocol template double creation.

If the content is different warn the user and ask
whether it should continue with the database creation.

In order to allow container with special needs like
ROS requiring some read/write space, the Container
class now parses the new custom "beat.env.custom_tmpfs"
label and add the corresponding entries to the dictionnary
dedicated to them.

Fixes #106

The prefix is resynced after the CXX tests, therefore
ensure that the original root_folder setup is applied
again.

This avoids breaking tests when CXX tests run before
the raw access tests.

This field will allow database creator to specify
whether the raw data can be made directly accessible
to the algorithm execution container.

It's missing support for - in the author part of
algorithm author name.

Fixes #104

beat/beat.cmdline re-implements similar parts so
make them reusable

This will grab the version currently used for the test
and in this case with the root_folder entry fixed for
the tests.

This will allow to use them in the same temporary
folder used for other test data.

It's not handled in the setup/teardown of the test package.

This will avoid the docker daemon to create them
and make them belong to it and thus not properly
accessible if the daemon is root.

This will allow the docker tests to more easily setup and
cleanup its content.

While the folder is not used as these databases are generative
only, docker will create it anyway as mounting a non-exisiting
folder will trigger its creation with the daemon ownership
applied.

A new property in the execution configuration allows to
mount the various databases in the algorithm container
in a similar fashion as the database container. It will
only work for containers that needs to access datasets.

Fixes #103

At least in production, some issues happened that required
to have /tmp writable. To preserve the read-only state
of the container, use a small tmpfs that is enough for
the container to run. /run is another that might be needed
so make it part of the defaults used.

This test ensures that the setup feature works properly.

It has been the case for a while for beat/beat.backend.cxx>