beat issues
https://gitlab.idiap.ch/groups/beat/-/issues
2020-11-12T12:20:40Z
https://gitlab.idiap.ch/beat/beat.core/-/issues/104
Experiment global properties regex is wrong for algorithms name
2020-11-12T12:20:40Z
Samuel GAIST
Experiment global properties regex is wrong for algorithms name
The `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 GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/78
Database index generated files belongs to docker daemon user
2020-11-10T16:47:14Z
Samuel GAIST
Database index generated files belongs to docker daemon user
Which 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 GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/77
CXX algorithm cannot be correctly downloaded
2020-11-10T16:42:45Z
Samuel GAIST
CXX algorithm cannot be correctly downloaded
The way the URL is built is wrong, it hardcodes the current use as the author which is not necessarily true.
The way the URL is built is wrong, it hardcodes the current use as the author which is not necessarily true.
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.core/-/issues/59
Tight "soft-loops" controlling algorithmic training
2020-11-04T17:09:18Z
André Anjos
Tight "soft-loops" controlling algorithmic training
In the context of the ALLIES project, a so-far-avoided requirement has popped up again the meeting: block loops.
I created this bug to differentiate from #29, because the requirements here are a bit different: in the use-case to be cons...
In the context of the ALLIES project, a so-far-avoided requirement has popped up again the meeting: block loops.
I created this bug to differentiate from #29, because the requirements here are a bit different: in the use-case to be considered, platform users need to be able to train a model depending on the output of another block. The main research question of the project needs to answer is: is it possible to implement life-long learning systems (LLLS) that can be taught by a human and improve over time? The outcome of the project must be reproducible (therefore our involvement).
In order to simulate this, partners provided the following diagram:
![modes](/uploads/a4e1aa953cd2bced7fa834da5d300e63/modes.png)
On the left, you'll see conventional ways to "adapt" statistical models from new input data. Given the model and more data, the model can be adapted to new incoming information (a.k.a. "source" in these diagrams).
In the context of ALLIES, partners want to have reproducible toolchains that allow third-parties to create the training system on the right of this image. In this context, the yellow boxes under the "training" (cyan) boxes simulate a human-user interaction with the system. E.g.: it could be a human telling a machine translation system the translation of a sentence (or paragraph) needs to be corrected, alongside with the correction, or it could be a human telling a speaker diarization system that a certain segment belongs to a different speaker. Because humans have limited ability to provide corrections, the consortium wants to control the implementation and limits of the "yellow" boxes, while third-parties implement the "trainers" that go into the cyan boxes.
It is possible to "unroll" these loops for practical scenarios, but in order to test limits of LLLS, one can envisage hundreds if not thousand iterations which is not very practical to code in BEAT as of today.
One of the key questions while considering #29 was that of the cache: a system that loops will issue multiply different cache outputs which, using the current architecture, would have to be kept. In this new use-case, such a caching requirement is not present. Partners only want to ensure that the code in "yellow" boxes can be properly tagged by the consortium and that they can conduct searches and build leaderboards on experiments using those (and only those). This prevents implementors of the "cyan" training boxes to misinterpret the role and data from the simulated human (yellow boxes). As a consequence, **no caching is required within this loop**.
Soft loops
https://gitlab.idiap.ch/beat/beat.web/-/issues/571
Two Factor Authentication
2020-10-21T10:11:02Z
Samuel GAIST
Two Factor Authentication
Since the platform is storing user data, it would be a welcomed addition for them to be able to secure their account using two factor authentication.
This should have no impact on the API since a token is used to communicate with the se...
Since the platform is storing user data, it would be a welcomed addition for them to be able to secure their account using two factor authentication.
This should have no impact on the API since a token is used to communicate with the service.
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.editor/-/issues/258
Documentation still points to the v1 editor components
2020-10-16T15:25:30Z
Amir MOHAMMADI
Documentation still points to the v1 editor components
Looking at the docs, it looks like the documentation was not updated for v2 release.
Given that users are installing v2 now, the docs need to be updated.
* [ ] Docs in this package
* [ ] Docs in `beat/docs`
Looking at the docs, it looks like the documentation was not updated for v2 release.
Given that users are installing v2 now, the docs need to be updated.
* [ ] Docs in this package
* [ ] Docs in `beat/docs`
https://gitlab.idiap.ch/beat/beat.web/-/issues/572
Dataformat edition removal
2020-10-06T09:55:00Z
Samuel GAIST
Dataformat edition removal
This issue tracks the work to make the dataformat part read-only
This issue tracks the work to make the dataformat part read-only
Read-only platform
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/573
Library edition removal
2020-10-06T09:54:59Z
Samuel GAIST
Library edition removal
This issue tracks the work to make the library part read-only
This issue tracks the work to make the library part read-only
Read-only platform
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/574
Algorithm edition removal
2020-10-06T09:54:58Z
Samuel GAIST
Algorithm edition removal
This issue tracks the work to make the algorithm part read-only
This issue tracks the work to make the algorithm part read-only
Read-only platform
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/575
Toolchain edition removal
2020-10-06T09:54:57Z
Samuel GAIST
Toolchain edition removal
This issue tracks the work to make the toolchain part read-only
This issue tracks the work to make the toolchain part read-only
Read-only platform
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/576
Experiment edition removal
2020-10-06T09:54:57Z
Samuel GAIST
Experiment edition removal
This issue tracks the work to make the experiment part read-only
This issue tracks the work to make the experiment part read-only
Read-only platform
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/578
Removed edition related documentation
2020-10-06T09:54:56Z
Samuel GAIST
Removed edition related documentation
As part of %"Read-only platform" the documentation related to the online edition of BEAT assets must be removed.
As part of %"Read-only platform" the documentation related to the online edition of BEAT assets must be removed.
Read-only platform
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/558
Fix usage of URL_PREFIX
2020-09-28T13:38:15Z
Samuel GAIST
Fix usage of URL_PREFIX
Currently the URL_PREFIX settings variable is used like a fully qualified URL in many parts of the website which is wrong. As the name suggests, this prefix shall essentially "move" all the URLs of the site behind it.
If a fully qualifi...
Currently the URL_PREFIX settings variable is used like a fully qualified URL in many parts of the website which is wrong. As the name suggests, this prefix shall essentially "move" all the URLs of the site behind it.
If a fully qualified address is needed it should be generated either using the request object associated with the method call or using Django's Sites framework.
This issue tracks the cleanup of the following:
- [x] Email generation
- [x] Template rendering
- [x] Other usages
Django 3 migration
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.web/-/issues/560
E-mail confirmations not containing the URL prefix and User links on the website
2020-09-28T13:37:32Z
Flavio TARSETTI
E-mail confirmations not containing the URL prefix and User links on the website
Issues with e-mail confirmations need to be checked as they don't contain the URL prefix and User links on the website.
On a local instance of beat.web this works, but it fails on the production platform. This seems to be a Django rel...
Issues with e-mail confirmations need to be checked as they don't contain the URL prefix and User links on the website.
On a local instance of beat.web this works, but it fails on the production platform. This seems to be a Django related issue as a first guess.
A similar problem also seem to happen with "experiments".
Might be related to #558 and #561
Django 3 migration
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.web/-/issues/559
Python 2 Code removal
2020-09-28T13:36:53Z
Samuel GAIST
Python 2 Code removal
Currently beat/beat.web> code is still compatible with Python 2.
The infrastructure has been running Python 3 for several years and moving to Django 3 implies that Python 2 is now out of question.
This issue tracks the work of removing...
Currently beat/beat.web> code is still compatible with Python 2.
The infrastructure has been running Python 3 for several years and moving to Django 3 implies that Python 2 is now out of question.
This issue tracks the work of removing all the compatibility code that has not been used for years and that will not be used anymore.
Django 3 migration
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/569
Deletion of migration patch for current users to the supervision system
2020-09-28T13:36:52Z
Flavio TARSETTI
Deletion of migration patch for current users to the supervision system
The migration patch ecosystem that was used to warn current users of the new supervision system needs to be removed as it unused and it no longer makes sense to keep it in the repository.
The following migrations need to be adjusted to ...
The migration patch ecosystem that was used to warn current users of the new supervision system needs to be removed as it unused and it no longer makes sense to keep it in the repository.
The following migrations need to be adjusted to accommodate with this.
The email generated for this need to be removed too.
Django 3 migration
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.web/-/issues/565
Admin: Environments are not clearly shown
2020-09-28T13:36:52Z
Flavio TARSETTI
Admin: Environments are not clearly shown
For Environments: The environment languages displayed for each environment is unclear:
We have like
```
Language:
Python
Python
Python
Python
That's very confusing.
```
For Environments: The environment languages displayed for each environment is unclear:
We have like
```
Language:
Python
Python
Python
Python
That's very confusing.
```
Code cleanup
https://gitlab.idiap.ch/beat/beat.web/-/issues/568
Crash on new supervisor sign-up
2020-09-28T13:36:52Z
Flavio TARSETTI
Crash on new supervisor sign-up
The application crashes with a `django.contrib.auth.models.User.DoesNotExist: User matching query does not exist.` when signing-up as a new supervisor.
This issue has shown up after the shift to Django 3
The application crashes with a `django.contrib.auth.models.User.DoesNotExist: User matching query does not exist.` when signing-up as a new supervisor.
This issue has shown up after the shift to Django 3
Django 3 migration
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.web/-/issues/561
Update dependencies to Django 3
2020-09-28T13:36:49Z
Samuel GAIST
Update dependencies to Django 3
The version of Django currently used by the platform is outdated.
This issue tracks the update of the Django as well as its dependencies to a current and maintained version.
The version of Django currently used by the platform is outdated.
This issue tracks the update of the Django as well as its dependencies to a current and maintained version.
Django 3 migration
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/570
Fix url prefix usage in yearly account revalidation command
2020-09-28T13:36:45Z
Flavio TARSETTI
Fix url prefix usage in yearly account revalidation command
The command and message needs to be updated to fix the url prefix usage.
The command and message needs to be updated to fix the url prefix usage.
Django 3 migration
Flavio TARSETTI
Flavio TARSETTI