beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2022-02-24T09:03:39Zhttps://gitlab.idiap.ch/beat/beat.core/-/issues/108Nightlies are failing for several reasons2022-02-24T09:03:39ZSamuel GAISTNightlies are failing for several reasonsThe nightlies are currently failing for several unrelated reasons:
- Looks like some keys have gone missing
- Some tests cannot be run because of database environment missing.
The first one is likely related to the use of cgroup v2 bas...The nightlies are currently failing for several unrelated reasons:
- Looks like some keys have gone missing
- Some tests cannot be run because of database environment missing.
The first one is likely related to the use of cgroup v2 based on the name of the fields missing and the information given on the [Container Stats information for the Docker v1.41 API](https://docs.docker.com/engine/api/v1.41/#operation/ContainerStats).
As for the database environments, the likely reasons is that all the runners and test machines had previous versions of the database images and thus the tests were run successfully although the test image pull method used later versions of them.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/docs/-/issues/18Job Failed #2473632021-11-03T16:55:42ZAmir MOHAMMADIJob Failed #247363Job [#247363](https://gitlab.idiap.ch/beat/docs/-/jobs/247363) failed for e93323cf9e36cd9c5ef91dee850e39af7ccc2ea1:
Needs `yum_requirements.txt`Job [#247363](https://gitlab.idiap.ch/beat/docs/-/jobs/247363) failed for e93323cf9e36cd9c5ef91dee850e39af7ccc2ea1:
Needs `yum_requirements.txt`Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/107Error on docker client creation2021-04-13T12:14:32ZSamuel GAISTError on docker client creationAt least on macOS when the daemon is not running, the client creation may fail and thus lead to an exception.
This is a case that is not yet handled like the others that follows when looking up for images.
Related to beat/beat.editor#282At least on macOS when the daemon is not running, the client creation may fail and thus lead to an exception.
This is a case that is not yet handled like the others that follows when looking up for images.
Related to beat/beat.editor#282Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/282Editor will not start if Docker is not running2021-04-13T12:14:31ZAndré AnjosEditor will not start if Docker is not runningThis either needs fixing and a better error message. Currently, the editor only reports `Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory'))`.This either needs fixing and a better error message. Currently, the editor only reports `Error while fetching server API version: ('Connection aborted.', FileNotFoundError(2, 'No such file or directory'))`.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/docs/-/issues/17`beat editor serve` does not exist anymore2021-04-08T12:14:33ZAndré Anjos`beat editor serve` does not exist anymoreThere is a small typo on the front installation page referenced from other guides. It states `beat editor serve` should be available. Given the change in the editor strategy, I think it should read `beat editor start`.There is a small typo on the front installation page referenced from other guides. It states `beat editor serve` should be available. Given the change in the editor strategy, I think it should read `beat editor start`.https://gitlab.idiap.ch/beat/beat.tutorial.prefix/-/issues/4Missing documentation2021-02-25T16:41:23ZSamuel GAISTMissing documentationDocumentations are missing for the following algorithms:
- linear_machine_learning_and_comparison
- facenet_project_and_comparison
- mnist_tester
A short description in the corresponding .json description would also be good.
There's n...Documentations are missing for the following algorithms:
- linear_machine_learning_and_comparison
- facenet_project_and_comparison
- mnist_tester
A short description in the corresponding .json description would also be good.
There's no need for a full paper about them but documenting what they do and their purpose will allow to generate the appropriate information for the AI4EU Acumos platform as well as make them visible on the BEAT platform.https://gitlab.idiap.ch/beat/beat.web/-/issues/586Database v2 handling2021-02-05T12:32:38ZSamuel GAISTDatabase v2 handlingDatabases object have seen a new version since beat/beat.core#64.
However the online platform does not handle yet the protocol template objects relate to the version 2 of the database object.
This ticket tracks the work relate to that....Databases object have seen a new version since beat/beat.core#64.
However the online platform does not handle yet the protocol template objects relate to the version 2 of the database object.
This ticket tracks the work relate to that.
Tasks to be done:
* [x] Implement application for handling ProtocolTemplate object
* [x] Implement installation of protocol templates
* [x] Implement handling of database v2 in the databases application
* [x] Ensure execution of experiment can continue with both v1 and v2 databases
This work will need update to the initial data provided through beat/beat.examples>Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat_exporter/-/issues/2Acumos databroker creation2021-01-18T12:49:29ZSamuel GAISTAcumos databroker creationDatabroker are data sources for the Acumos platform.
It is not mandatory to create these blocks however, they are likely going to be needed in order for people to be able to more easily test the implementation of the BEAT exported "mode...Databroker are data sources for the Acumos platform.
It is not mandatory to create these blocks however, they are likely going to be needed in order for people to be able to more easily test the implementation of the BEAT exported "models".
This task tracks the work related to the creation of a script that will automate the process to create a Docker image that should be usable as data broker.
Currently information is sparse about how a data broker should be identified and how it is supposed to work.
Based on email message exchange done with Martin Weiss, the data broker shall notify the system that is have provided everything it has be returning an empty answer.Implement databroker creationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat_exporter/-/issues/1Acumos "model" creation2021-01-18T12:50:34ZSamuel GAISTAcumos "model" creationAI4EU computing assets are called "models".
This task tracks the work related to the creation of a tool that will allow the creation of docker images out of BEAT algorithms.
Note that not all BEAT algorithms are eligible for exportatio...AI4EU computing assets are called "models".
This task tracks the work related to the creation of a tool that will allow the creation of docker images out of BEAT algorithms.
Note that not all BEAT algorithms are eligible for exportation to an Acumos compatible Docker image.
Based on the current state of the platform as of 18.01.2021, here is a list of the constraints that must be taken into account:
The current Acumos orchestrator follows a single input single output sequential execution implementation. This means that each data frame coming from the entry data broker will have to pass through all the blocks from a solution up to its final block before processing the next data frame.
This means that there's no training currently possible within the Acumos platform.
Therefore in terms of BEAT algorithms, this means that only algorithms matching the following criteria can be used:
- Only sequential algorithms can be used as autonomous ones uses pull rather than a push to get data which is not available currently in Acumos
- Only algorithms which write as many outputs as they gets inputs as otherwise the orchestrator won't be able to carry on a full run
These criteria may change in the future based on the features implemented on Acumos.
It has also been decided that in the first iteration, the tool that will export the BEAT algorithm will only be used locally. Therefore no online platform data extraction will happen.
This means that a user will first have to run a full experiment using the algorithm(s) destinated to be exported before the tool can be used.Implement algorithm export to acumosSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/585Add expiration date and alternative procedure for email accounts holding temp...2021-01-18T15:00:52ZFlavio TARSETTIAdd expiration date and alternative procedure for email accounts holding temporary URLsOn specific emails that target users accounts, temporary URLs were used to simplify the a user action.
However the expiration date of the temporay URL is not mentioned and an alternative procedure is not present to help the user realize...On specific emails that target users accounts, temporary URLs were used to simplify the a user action.
However the expiration date of the temporay URL is not mentioned and an alternative procedure is not present to help the user realize manually the required operation.Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/584Disable signup page access for already logged in user2021-01-08T14:11:36ZSamuel GAISTDisable signup page access for already logged in userThis should not be accessible when users are already logged in.This should not be accessible when users are already logged in.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/583Password reset triggers internal error2021-01-07T10:06:51ZSamuel GAISTPassword reset triggers internal errorUsing the password reset form with a valid email address triggers an internal server error.Using the password reset form with a valid email address triggers an internal server error.Code cleanupSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/581Changing password doesn't proceed with a proper logout2020-12-16T10:01:25ZFlavio TARSETTIChanging password doesn't proceed with a proper logoutChanging password from the user settings doesn't proceed with a proper `logout` which in turns result by letting the possibility to click on any buttong and end up on a `Not Found` page. The user then needs to go back to the website to s...Changing password from the user settings doesn't proceed with a proper `logout` which in turns result by letting the possibility to click on any buttong and end up on a `Not Found` page. The user then needs to go back to the website to see that he's logged out.
Expected behavior:
Change your password -> get logged out -> refresh the pageSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/580Safari issue with https://beat-eu.org and https://www.beat-eu.org/2020-12-16T15:09:00ZFlavio TARSETTISafari issue with https://beat-eu.org and https://www.beat-eu.org/Important note: This issue targets the browser Safari for Mac Users. I am unable to reproduce it via Chrome on Linux.
Login via https://beat-eu.org doesn't get you logged in while logging in via https://www.beat-eu.org/ does work fine....Important note: This issue targets the browser Safari for Mac Users. I am unable to reproduce it via Chrome on Linux.
Login via https://beat-eu.org doesn't get you logged in while logging in via https://www.beat-eu.org/ does work fine.
Could maybe be related to 2FA but maybe not.https://gitlab.idiap.ch/beat/beat.core/-/issues/106ROS specific needs2020-11-30T08:50:02ZSamuel GAISTROS specific needsRequirement
===========
In the scope of the learn-real project, ROS is one of the possible system used however it needs to write some files (pids, small logs, etc.) in order to run properly however these can be discarded when the run en...Requirement
===========
In the scope of the learn-real project, ROS is one of the possible system used however it needs to write some files (pids, small logs, etc.) in order to run properly however these can be discarded when the run ends.
The current estimation done by @cazinn for the space needed is about 10Mb.
The ROS main folder is `~.ros` by default and that can be changed using the [ROS_HOME environment variable](http://wiki.ros.org/ROS/EnvironmentVariables#System_Data_Environment_Variables).
Current situation
=================
For security reasons, our containers are run in read-only mode with two small read/write tmpfs mounted on the containers: /tmp and /var. Each of which is allocated 500kb which is enough for the use of BEAT.
We do have support for adding temporary volumes in place as well as setting custom environment variables.
Possible solutions
==================
In order to run Docker containers that can execute ROS, we have several possibilities:
1) Mount a tmpfs volume on the default ROS home folder
2) Make either the `/tmp` or `/var` volumes bigger and point `ROS_HOME` in a subfolder in them
3) Add a new tmpfs volume in a separated known folder and point `ROS_HOME` to it
`ROS_HOME` can either be hardcoded during the image creation process or dynamically set when running the container.
Main questions
==============
For solution 1, from where should the information about the size of the target folder come from as well as the target location ?
For solution 2, `ROS_HOME` can be hardcoded as part of the image creation
For solution 3, same questions as for solution 1 with the possibility of hardcoding the environment variable as in solution 2.André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/79Remove database sharing explicit option2020-11-16T14:34:22ZSamuel GAISTRemove database sharing explicit optionFollowing the discussion on beat/beat.web!410, the database raw data sharing implementation was change and its definition moved to the database declaration.
beat/beat.core!132 implements that.
Therefore remove the explicit database sha...Following the discussion on beat/beat.web!410, the database raw data sharing implementation was change and its definition moved to the database declaration.
beat/beat.core!132 implements that.
Therefore remove the explicit database sharing option here as it is not used anymore.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/105Refactor database sharing2020-11-17T12:09:23ZSamuel GAISTRefactor database sharingFollowing discussion on beat/beat.web!410, the database sharing feature will be refactored with the following:
- Add a new `direct_rawdata_access` optional field to the database schema
- Use that in place of the optional "share_databases...Following discussion on beat/beat.web!410, the database sharing feature will be refactored with the following:
- Add a new `direct_rawdata_access` optional field to the database schema
- Use that in place of the optional "share_databases" external field
- The field will apply to both v1 and v2 Database schema
- Support for optional field allows to keep the current databases workingSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/579Add support for setting up sharing of dataset content with algorithm container2020-11-17T12:06:35ZSamuel GAISTAdd support for setting up sharing of dataset content with algorithm containerFollowing the work started in beat/beat.core#103, implement a solution that allows to configure block execution that will share databases both with the database container and the algorithm container.Following the work started in beat/beat.core#103, implement a solution that allows to configure block execution that will share databases both with the database container and the algorithm container.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/104Experiment global properties regex is wrong for algorithms name2020-11-12T12:20:40ZSamuel GAISTExperiment global properties regex is wrong for algorithms nameThe `patternProperties` definition for algorithm related properties is missing `-` for the author part of the regex so it forbids creating experiments using valid algorithms.The `patternProperties` definition for algorithm related properties is missing `-` for the author part of the regex so it forbids creating experiments using valid algorithms.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/78Database index generated files belongs to docker daemon user2020-11-10T16:47:14ZSamuel GAISTDatabase index generated files belongs to docker daemon userWhich makes them belonging to root currently which is wrong.
It should be the user which currently runs the indexing or a specific UID.Which makes them belonging to root currently which is wrong.
It should be the user which currently runs the indexing or a specific UID.Samuel GAISTSamuel GAIST