beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2020-08-06T08:41:49Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/275TypeError: %d format: a number is required, not NoneType2020-08-06T08:41:49ZAmir MOHAMMADITypeError: %d format: a number is required, not NoneTypeSteps to reproduce:
1. open a v1 alg in the editor: [livdet_baseline.tar.xz](/uploads/2e239002e1c600fe44c57b67005b5817/livdet_baseline.tar.xz)
2. answer yes to its migration to v2
3. save it:
```
Traceback (most recent call last):
File...Steps to reproduce:
1. open a v1 alg in the editor: [livdet_baseline.tar.xz](/uploads/2e239002e1c600fe44c57b67005b5817/livdet_baseline.tar.xz)
2. answer yes to its migration to v2
3. save it:
```
Traceback (most recent call last):
File "/home/amir/miniconda/envs/iris/lib/python3.7/site-packages/beat/editor/widgets/assetwidget.py", line 520, in saveJson
is_valid, errors = self.current_asset.is_valid()
File "/home/amir/miniconda/envs/iris/lib/python3.7/site-packages/beat/editor/backend/asset.py", line 269, in is_valid
_, error_list = self.type.validate(self.declaration_path)
File "/home/amir/miniconda/envs/iris/lib/python3.7/site-packages/beat/editor/backend/asset.py", line 112, in validate
return validate(self.name.lower(), data)
File "/home/amir/miniconda/envs/iris/lib/python3.7/site-packages/beat/core/schema/__init__.py", line 176, in validate
validator = load_schema(schema_name, version)
File "/home/amir/miniconda/envs/iris/lib/python3.7/site-packages/beat/core/schema/__init__.py", line 93, in load_schema
__name__, os.path.join(schema_name, "%d.json" % version)
TypeError: %d format: a number is required, not NoneType
```Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/227Feature request: Search functionality when making a new version or fork an as...2020-08-06T09:10:07ZZohreh MOSTAANIFeature request: Search functionality when making a new version or fork an asset.It would be good to be able to search for the asset you want to fork or make a new version since the existing list can be very long.It would be good to be able to search for the asset you want to fork or make a new version since the existing list can be very long.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/246Correct base types management in AssetModel2020-08-10T08:39:27ZSamuel GAISTCorrect base types management in AssetModelSummary
The DataFormat base types provided through AssetModel shall not be used everywhere a DataFormat is used.
An analysis must be done to determine where exactly it make sense to have them and also if they must be made availble toge...Summary
The DataFormat base types provided through AssetModel shall not be used everywhere a DataFormat is used.
An analysis must be done to determine where exactly it make sense to have them and also if they must be made availble together with the other Dataformats provided by the prefix.
AssetModel shall be purged from these types and a dedicated subclass created if it makes sense to provide them all in one or more places in the code.
Depending also on whether these base types should be the only type used, another model might be created or [QStringListModel](https://doc.qt.io/qt-5/qstringlistmodel.html) used directly in these cases.[v2] 1 - Edition/Visualization for small editorsFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/185Experiment Editor2020-08-10T12:44:08ZJaden DIEFENBAUGHExperiment EditorThis issue tracks the implementation of the experiment editor.
As this editor is more complex regarding object management as well as setup, the work will be done in several steps:
* [x] Blocks edition
* [x] Toolchain preview
* [x] S...This issue tracks the implementation of the experiment editor.
As this editor is more complex regarding object management as well as setup, the work will be done in several steps:
* [x] Blocks edition
* [x] Toolchain preview
* [x] Smart filtering
Unlike all other BEAT assets, creating a new experiment requires an additional step therefore, a dedicated task is needed with regard to the creation of such a new asset:
* [x] Add support for new experiment creation to asset dialog[v2] 3 - Experiment editorSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/243There is no way to close an asset without opening another one.2020-08-10T15:27:51ZZohreh MOSTAANIThere is no way to close an asset without opening another one.At the moment at all the times there should be one asset opened (except for when the editor starts).
It might be useful to add a button to close an asset without opening a new one. It might also be useful in the future if multiple insta...At the moment at all the times there should be one asset opened (except for when the editor starts).
It might be useful to add a button to close an asset without opening a new one. It might also be useful in the future if multiple instances/windows of editor are open.https://gitlab.idiap.ch/beat/beat.web/-/issues/562Pre-commit cleanup2020-09-11T15:54:25ZSamuel GAISTPre-commit cleanupThe current code base is pretty old and contains code that requires some cleanup.
The cleanup includes:
- Unused import
- Ordering of imports
- Unused code
- Possible coding issue
This list is not exhaustive.
The cleanup shall be done...The current code base is pretty old and contains code that requires some cleanup.
The cleanup includes:
- Unused import
- Ordering of imports
- Unused code
- Possible coding issue
This list is not exhaustive.
The cleanup shall be done using pre-commit hooks that include:
- black
- isort
- bandit
- flake8
And possibly others if relevant tools are found in the process.Code cleanupSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/564Crash in some admin pages2020-09-11T15:56:04ZSamuel GAISTCrash in some admin pagesWhen trying to go to an admin page that shows a beat asset, the site crashes because of a missing parameter.When trying to go to an admin page that shows a beat asset, the site crashes because of a missing parameter.Django 3 migrationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/566Asset files are read in templates rather than using the proper property2020-09-17T14:14:18ZSamuel GAISTAsset files are read in templates rather than using the proper propertyAsset having files have are related properties that handles the data loading.
Several templates use the file object directly rather than the property which has as side effect of depending on the default mode used to open the file.
Curr...Asset having files have are related properties that handles the data loading.
Several templates use the file object directly rather than the property which has as side effect of depending on the default mode used to open the file.
Currently it looks like the mode is binary and thus the rendering is wrong.
Related to !358Code cleanupSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/570Fix url prefix usage in yearly account revalidation command2020-09-28T13:36:45ZFlavio TARSETTIFix url prefix usage in yearly account revalidation commandThe 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 migrationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/561Update dependencies to Django 32020-09-28T13:36:49ZSamuel GAISTUpdate dependencies to Django 3The 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 migrationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/568Crash on new supervisor sign-up2020-09-28T13:36:52ZFlavio TARSETTICrash on new supervisor sign-upThe 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 3The 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 3Django 3 migrationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/565Admin: Environments are not clearly shown2020-09-28T13:36:52ZFlavio TARSETTIAdmin: Environments are not clearly shownFor 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 cleanuphttps://gitlab.idiap.ch/beat/beat.web/-/issues/569Deletion of migration patch for current users to the supervision system2020-09-28T13:36:52ZFlavio TARSETTIDeletion of migration patch for current users to the supervision systemThe 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 migrationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/559Python 2 Code removal2020-09-28T13:36:53ZSamuel GAISTPython 2 Code removalCurrently 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 migrationSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/560E-mail confirmations not containing the URL prefix and User links on the website2020-09-28T13:37:32ZFlavio TARSETTIE-mail confirmations not containing the URL prefix and User links on the websiteIssues 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 migrationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/558Fix usage of URL_PREFIX2020-09-28T13:38:15ZSamuel GAISTFix usage of URL_PREFIXCurrently 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 usagesDjango 3 migrationFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/578Removed edition related documentation2020-10-06T09:54:56ZSamuel GAISTRemoved edition related documentationAs 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 platformSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/576Experiment edition removal2020-10-06T09:54:57ZSamuel GAISTExperiment edition removalThis issue tracks the work to make the experiment part read-onlyThis issue tracks the work to make the experiment part read-onlyRead-only platformSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/575Toolchain edition removal2020-10-06T09:54:57ZSamuel GAISTToolchain edition removalThis issue tracks the work to make the toolchain part read-onlyThis issue tracks the work to make the toolchain part read-onlyRead-only platformSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/574Algorithm edition removal2020-10-06T09:54:58ZSamuel GAISTAlgorithm edition removalThis issue tracks the work to make the algorithm part read-onlyThis issue tracks the work to make the algorithm part read-onlyRead-only platformSamuel GAISTSamuel GAIST