beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2020-03-03T13:45:06Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/254PyPI classifier designation update for GPL v3 licenses2020-03-03T13:45:06ZFlavio TARSETTIPyPI classifier designation update for GPL v3 licensesSummary
PyPI has changed its classifier designation for GPL v3 licences
What is the current bug behavior?
The current bug is shown in this release pipeline:
https://gitlab.idiap.ch/beat/beat.editor/pipelines/37844
and specifically i...Summary
PyPI has changed its classifier designation for GPL v3 licences
What is the current bug behavior?
The current bug is shown in this release pipeline:
https://gitlab.idiap.ch/beat/beat.editor/pipelines/37844
and specifically in the following job
https://gitlab.idiap.ch/beat/beat.editor/-/jobs/191064
where an error is thrown:
```
requests.exceptions.HTTPError: 400 Client Error: Invalid value for classifiers.
Error: 'License :: OSI Approved :: GNU General Public License v3' is not a valid choice
for this field for url: https://upload.pypi.org/legacy/ 515
```
What is the expected correct behavior?
It shouldn't fail on this deployment part on PyPI
Relevant logs and/or screenshots
- https://gitlab.idiap.ch/beat/beat.editor/pipelines/37844
- https://gitlab.idiap.ch/beat/beat.editor/-/jobs/191064
Possible fixes
This faulty line in `setup.py`:
**"License :: OSI Approved :: GNU General Public License v3"**
should become:
**"License :: OSI Approved :: GNU General Public License v3 (GPLv3)"**Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.core/-/issues/95Schema: missing constraints2020-03-10T16:08:31ZSamuel GAISTSchema: missing constraintsOn the platform, fields like the short descriptions have for example size constraints.
These should be reflected here to avoid issues when creating a new object.On the platform, fields like the short descriptions have for example size constraints.
These should be reflected here to avoid issues when creating a new object.https://gitlab.idiap.ch/beat/beat.web/-/issues/545Migration issue with the documentation2020-03-16T16:29:31ZFlavio TARSETTIMigration issue with the documentationBy moving from beat-eu.org to idiap.ch the link should be updated to target the documentation in the supervisor sign-up form.By moving from beat-eu.org to idiap.ch the link should be updated to target the documentation in the supervisor sign-up form.Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/544Improve sign-up form2020-03-16T16:29:31ZAndré AnjosImprove sign-up formCurrently, the sign-up form for supervisors does not indicate that one must use their "institutional" e-mail address. I propose we modify it slightly to indicate this as well as include an URL to the reasoning behind this.
For example:...Currently, the sign-up form for supervisors does not indicate that one must use their "institutional" e-mail address. I propose we modify it slightly to indicate this as well as include an URL to the reasoning behind this.
For example:
* Instead of saying "you hold a position in a research laboratory", we should say "you hold a permanent position in a research laboratory".
* Instead of saying "E-mail" we should say "Institutional E-mail".
* We should add a link to: https://www.idiap.ch/software/beat/docs/beat/docs/stable/beat.web/doc/user/faq.html#what-is-a-supervisor
* In that link, we should specify that e-mail should be institutional.Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/65Improve dependency check tests2020-03-16T17:16:29ZFlavio TARSETTIImprove dependency check testsTests are missing.
Related to https://gitlab.idiap.ch/beat/beat.cmdline/merge_requests/86Tests are missing.
Related to https://gitlab.idiap.ch/beat/beat.cmdline/merge_requests/86Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/66Experiment monitor command is broken2020-03-18T12:07:14ZSamuel GAISTExperiment monitor command is brokenThe experiment monitor command does not work anymore following the cleanup of the webapi module.
The get is still handled old style.The experiment monitor command does not work anymore following the cleanup of the webapi module.
The get is still handled old style.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/255Ensure field max length is respected2020-03-25T11:42:34ZSamuel GAISTEnsure field max length is respectedThe short description field has a maximal length on the platform that must checked here.
There editors should implement these constraints.
If possible these constraints should also be encoded in the corresponding schemas and the variou...The short description field has a maximal length on the platform that must checked here.
There editors should implement these constraints.
If possible these constraints should also be encoded in the corresponding schemas and the various editors use that information to enforce them.
See beat/beat.core#95Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/256Toolchain tests for BlockType class2020-03-26T12:44:59ZFlavio TARSETTIToolchain tests for BlockType classSummary
Tests for possible block type objects are missing for the toolchain editorSummary
Tests for possible block type objects are missing for the toolchain editorFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/515BEAT website certificate and expiration2020-03-30T14:04:20ZAndré AnjosBEAT website certificate and expirationThe BEAT website certificate will expire in March 2020. The domain name will not be renewed, so we need to migrate the location of the official platform (beat.web production deployment).
To avoid a pressing issue then, and leave time f...The BEAT website certificate will expire in March 2020. The domain name will not be renewed, so we need to migrate the location of the official platform (beat.web production deployment).
To avoid a pressing issue then, and leave time for people to "adapt" to a new address, I propose we start looking for solutions now.
@samuel.gaist: Could you please contact the system group (via a ticket) and ask them which solutions could be setup to host the platform under "idiap.ch".
I thought of 2 options, but I'm not sure whether these are feasible:
1. "https://beat.idiap.ch": The advantage is that swagger docs would start working again...
2. "https://www.idiap.ch/software/beat/platform": This would be the one that makes more sense "structurally"Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/495Expose more info about the available environments from the REST API2020-03-30T15:38:45ZJaden DIEFENBAUGHExpose more info about the available environments from the REST APIRight now we get something like this:
```json
[
{
"name": "Cxx backend",
"queues": {
"queue": {
"memory_limit": 1985,
"nb_slots": 0,
"max_slots_per_user": 8,
"nb_cores_per_slot": 1,
...Right now we get something like this:
```json
[
{
"name": "Cxx backend",
"queues": {
"queue": {
"memory_limit": 1985,
"nb_slots": 0,
"max_slots_per_user": 8,
"nb_cores_per_slot": 1,
"time_limit": 1440
}
},
"accessibility": "public",
"languages": [
"cxx"
],
"version": "1.1.0",
"short_description": "C++ backend"
},
{
"name": "Python 2.7",
"queues": {
"queue": {
"memory_limit": 1985,
"nb_slots": 0,
"max_slots_per_user": 8,
"nb_cores_per_slot": 1,
"time_limit": 1440
}
},
"accessibility": "public",
"languages": [
"python"
],
"version": "1.2.0",
"short_description": "Local python interpreter"
}
]
```
We need to add a "modules" field to the environments that lists packages & versions that are available. It would look something like this:
```json
[
...
{
"name": "Python 2.7",
...
"packages": {
"alabaster": "0.7.10",
"Babel": "2.4.0",
...
},
"version": "1.2.0",
"short_description": "Local python interpreter"
}
]
```
This is needed for the June 2018 deliverable!https://gitlab.idiap.ch/beat/beat.web/-/issues/546Improve experiment finished email2020-04-01T09:50:27ZSamuel GAISTImprove experiment finished emailCurrently, the emails sent to platform users for notification about a run success or failure contains a direct link that will end in a 404 error if the user is not logged in.
It would be nice if the link would allow to start the login p...Currently, the emails sent to platform users for notification about a run success or failure contains a direct link that will end in a 404 error if the user is not logged in.
It would be nice if the link would allow to start the login process since it is sent to the author of the experiment.Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/548API for compatibility information about an algorithm2020-04-07T20:26:11ZSamuel GAISTAPI for compatibility information about an algorithmThe detail page of an algorithm shows the information about which environments where used successfully to run that algorithm. The API currently does not offer that and it will be needed to create Docker container suitable for the AI4EU p...The detail page of an algorithm shows the information about which environments where used successfully to run that algorithm. The API currently does not offer that and it will be needed to create Docker container suitable for the AI4EU project.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/67Version information missing on push2020-04-14T14:43:26ZSamuel GAISTVersion information missing on pushWhen creating a new version of an algorithm or a fork, the version information is not pushed with the data.
It is currently not used by beat/beat.web> but this is about to change because the current way new version creation is handled i...When creating a new version of an algorithm or a fork, the version information is not pushed with the data.
It is currently not used by beat/beat.web> but this is about to change because the current way new version creation is handled is suboptimal. If for some reasons a new version is created manually rather than through "beat <asset_type> version`, the missing history version will trigger the creation of a new "version 1" asset or at least an attempt to do that.
See beat/beat.web#547Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/547Improve new version push handling2020-04-16T13:15:24ZSamuel GAISTImprove new version push handlingCurrently if a new version of an asset is pushed without history information, there will be an error because the backend will try to create an asset from scratch. This will trigger an error because of an already existing asset.
As a sid...Currently if a new version of an asset is pushed without history information, there will be an error because the backend will try to create an asset from scratch. This will trigger an error because of an already existing asset.
As a side effect, if no asset of a previous version exists, the backbend will create a new one based on the name but with the wrong number.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/549Expand required for supervision lists2020-05-06T07:32:29ZFlavio TARSETTIExpand required for supervision listsThe supervision lists should be expanded over multiple columns to improve its visibilityThe supervision lists should be expanded over multiple columns to improve its visibilityFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/538Moving cronjobs in beat.web to systemd2020-05-13T15:23:23ZAndré AnjosMoving cronjobs in beat.web to systemdI get repeated e-mails every day concerning our BEAT jobs in beat.web. After more than a year, these scripts are pretty stable and it would be nice if we managed to make them **not** report unless there is a problem (exit status != 0).
...I get repeated e-mails every day concerning our BEAT jobs in beat.web. After more than a year, these scripts are pretty stable and it would be nice if we managed to make them **not** report unless there is a problem (exit status != 0).
In our internal webserver, I managed to implement this using systemd (report on failure only).
Could we do the same here? That would avoid the continuous torrent of "successful run" e-mails.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/550Notify supervisor of supervisee yearly revalidation - Quick link to revoke su...2020-05-18T13:06:16ZFlavio TARSETTINotify supervisor of supervisee yearly revalidation - Quick link to revoke supervisionWhen a supervisee revalidates his account during a yearly revalidation process, the supervisor should be notifed in order to quickly check if the revalidation claim is based on proper supervision information.
The supervisor can drop the...When a supervisee revalidates his account during a yearly revalidation process, the supervisor should be notifed in order to quickly check if the revalidation claim is based on proper supervision information.
The supervisor can drop the email notification if all is correct or should be able to quickly revoke this supervision claim if needed through a temporary link given in the email.
Related to #542Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/542Improve automatic e-mails2020-05-18T13:06:17ZAndré AnjosImprove automatic e-mailsE-mails such as those for account revalidation do not embed an easy to use URL that, upon clicking, performs the action in question.
It would be be handy to have URLs in all such e-mails, for accepting or, sometimes, rejecting the actio...E-mails such as those for account revalidation do not embed an easy to use URL that, upon clicking, performs the action in question.
It would be be handy to have URLs in all such e-mails, for accepting or, sometimes, rejecting the action, if it makes sense.Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/551Blocked account login attempts2020-05-26T12:57:45ZFlavio TARSETTIBlocked account login attemptsIf an account is blocked (not revalidated), then password reactivation is not possible. In this case, it would be nice to receive an e-mail indicating that, instead, and what to do to re-activate the account.
We do not wish to inform on...If an account is blocked (not revalidated), then password reactivation is not possible. In this case, it would be nice to receive an e-mail indicating that, instead, and what to do to re-activate the account.
We do not wish to inform online that a successful attempt was made, but rather inform the person by email about this.Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/38Offline plotting support is shaky2020-05-26T15:19:19ZJaden DIEFENBAUGHOffline plotting support is shakyIf the plotter object and the default plotterparameters exist in the local prefix, failing to fetch info from the BEAT web platform should not stop plotting.
The issue came up when using the tutorial VM. Some people didn't have an inter...If the plotter object and the default plotterparameters exist in the local prefix, failing to fetch info from the BEAT web platform should not stop plotting.
The issue came up when using the tutorial VM. Some people didn't have an internet connection and couldn't plot because `beat.cmdline` was trying to fetch stuff from beat.web even though the plotter objects and default parameters existed.Samuel GAISTSamuel GAIST