beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2019-06-03T09:36:59Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/219AssetModel latest only feature is incomplete2019-06-03T09:36:59ZSamuel GAISTAssetModel latest only feature is incompleteSummary
The "latest only" property implement of AssetModel is currently incomplete and does not work for all asset types.
Steps to reproduce
```
model = AssetModel()
model.prefix_path = "path/to/prefix"
model.asset_type = "AssetType....Summary
The "latest only" property implement of AssetModel is currently incomplete and does not work for all asset types.
Steps to reproduce
```
model = AssetModel()
model.prefix_path = "path/to/prefix"
model.asset_type = "AssetType.DATAFORMAT"
asset_list = model.stringList()
model.setLatestOnlyEnabled(False)
full_asset_list = model.stringList()
assert asset_list != full_asset_list
assert len(asset_list) < len(full_asset_list)
```
What is the current bug behavior?
The same list of assets is returned for types that are neither database nor protocol templates.
What is the expected correct behavior?
The two lists should be different if the prefix contains several versions of these assets
Possible fixes
Implement the same "un-filtering" for all assets where it make sense.
The fix will require beat/beat.core!76[v2] 1 - Edition/Visualization for small editorsSamuel GAISTSamuel GAISThttps://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.editor/-/issues/221Open asset related files2019-10-04T15:12:53ZSamuel GAISTOpen asset related filesFiles related to the asset are currently not shown nor editable through beat/beat.editor>.
Add the possibility to edit these using the user's corresponding default editor.Files related to the asset are currently not shown nor editable through beat/beat.editor>.
Add the possibility to edit these using the user's corresponding default editor.[v2] 1 - Edition/Visualization for small editorsSamuel GAISTSamuel GAISThttps://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.editor/-/issues/222Database Editor: update naming for set2019-10-04T15:12:53ZFlavio TARSETTIDatabase Editor: update naming for setPatch typo name as possible confusion and collision with python "set" class.
Part of #183Patch typo name as possible confusion and collision with python "set" class.
Part of #183Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/223Remove unused code in protocol template editor2019-10-04T15:12:53ZFlavio TARSETTIRemove unused code in protocol template editorThis targets unused code from the plotter template editorThis targets unused code from the plotter template editorFlavio TARSETTIFlavio TARSETTIhttps://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.editor/-/issues/224Automatic conversion to v2 for databases2020-02-20T13:32:19ZZohreh MOSTAANIAutomatic conversion to v2 for databasesAt the moment all the database objects available in the test prefix (and probably the user's custom prefix) are not using "schema_version": 2. All the databases written in the previous version of the schema are read-only, therefore if a ...At the moment all the database objects available in the test prefix (and probably the user's custom prefix) are not using "schema_version": 2. All the databases written in the previous version of the schema are read-only, therefore if a user wants to make a new version of a database, it is again read-only (not editable) which defeats the purpose of making a new version!
It is reasonable that when the user makes a new version of a database, instead of ending up with a read-only file, a new file for the database using "schema_version": 2 is created.
It will be good also that a message is shown to the user that there is a change in the schema_version, so they are aware of the change, and they won't be surprised when they look at the json file.
Steps to reproduce:
- Open editor v2.
- Go to File -> New -> databases -> New version
- Click on Ok
the created database is read-only.https://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.editor/-/issues/225When opening a new algorithm, editor checks for "integer" dataformat that mig...2019-07-02T13:24:53ZZohreh MOSTAANIWhen opening a new algorithm, editor checks for "integer" dataformat that might not be available.When you try to make a new algorithm it gives and error "Reference dataformats [integer, integer] not found". The reason is that to make the correct template for the algorithm the editor checks for "integer" data format to exist, otherwi...When you try to make a new algorithm it gives and error "Reference dataformats [integer, integer] not found". The reason is that to make the correct template for the algorithm the editor checks for "integer" data format to exist, otherwise it gives an error. Even though the dataformat "integer" seems very obvious to be a part of a typical custom prefix, it is not the case.
There are two solutions to this problem:
1. When the user wants to make a new algorithm a message pops up and says "you need this, do you want me to create it"
2. At the beginning when the editor checks the sanity of the prefix the same window pops up. (similar to the behaviour regarding protocoltemplates)
Steps to reproduce:
- Open editor v2.
- Go to File -> New -> algorithm -> New.
- Press ok.
It gives the error "Reference dataformats [integer, integer] not found".
It should just make a new algorithm and such underlying issues should be transparent to the user as much as possible.Samuel 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.editor/-/issues/226When a new/new version of an asset is made, it is not obvious to the user sin...2019-10-04T15:12:51ZZohreh MOSTAANIWhen a new/new version of an asset is made, it is not obvious to the user since it doesn't pop open.At the moment, when you make a new/new version of a asset, it only creates a file in the corresponding directory, but it doesn't actually open the file in the editor, ready to be edited. The user needs to go back through the list of file...At the moment, when you make a new/new version of a asset, it only creates a file in the corresponding directory, but it doesn't actually open the file in the editor, ready to be edited. The user needs to go back through the list of files to find it and open it manually.
This approach not only is not intuitive, but also it can get very confusing very fast especially if you have so many assets with similar names. It is usually the case when you are testing experiments just with minor changes.https://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.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/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.editor/-/issues/229Adding the name of the asset being edited on the top of the edit/json widget2019-06-28T09:58:15ZZohreh MOSTAANIAdding the name of the asset being edited on the top of the edit/json widgetIt is necessary to have the name of the asset being edited somewhere on the right side of the editor. The reason is that at the moment if you have an asset open, and on the list of the assets on the left you click on some other thing, on...It is necessary to have the name of the asset being edited somewhere on the right side of the editor. The reason is that at the moment if you have an asset open, and on the list of the assets on the left you click on some other thing, only once (not double click), that object gets the focus but it is not open. Therefore what you see that is selected is not what is being actually edited.
The idea is to add the name of the asses on the top of the edit/json widget.
If we have the name there it will be useful if there are multiple windows open. see #228.Samuel 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.editor/-/issues/230Adding the name of the asset being saved to the dialogue box2019-07-05T14:43:55ZZohreh MOSTAANIAdding the name of the asset being saved to the dialogue boxAt the moment when you save an asset, it just says "Content changed. Do you want to save it?" But it doesn't give the name of the asset in question. This can become very confusing.
1. At the moment there is no name on the top of editor/...At the moment when you save an asset, it just says "Content changed. Do you want to save it?" But it doesn't give the name of the asset in question. This can become very confusing.
1. At the moment there is no name on the top of editor/json widget, and it is not obvious what is being changed. see #229 .
2. If there will be multiple windows in the future this feature is necessary. see #228 .Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/571Two Factor Authentication2020-10-21T10:11:02ZSamuel GAISTTwo Factor AuthenticationSince 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 GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/231The cleanup for the content widget is not done properly.2019-10-04T15:12:53ZZohreh MOSTAANIThe cleanup for the content widget is not done properly.The issue is that if you edit an asset (tested with dataformat), and then open another dataformat without saving the previous one the content of what you have opened past will be shown in the one that has not been saved, instead of it be...The issue is that if you edit an asset (tested with dataformat), and then open another dataformat without saving the previous one the content of what you have opened past will be shown in the one that has not been saved, instead of it being in the previous state.
I realize that you don't even need to make a new dataformat. To reproduce the issue, you just need to have several dataformat from one or more than one user available. Start opening them one after another and look at the change in the content!
The issue comes from how the widgets are being cleaned before a new asset is open. The content from previous asset is not cleaned fully and what you see as the newly open asset is not it's own content but information from the leftovers.Samuel GAISTSamuel GAIST