beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-04-14T11:55:44Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/107Re-using a saved search after platform update not working2015-04-14T11:55:44ZSébastien MARCELRe-using a saved search after platform update not workingon my Search tab https://www.beat-eu.org/platform/user/smarcel/?tab=searches
I am re-using a previous search by clicking to reach
https://www.beat-eu.org/platform/search/smarcel/MOBIO/
and I got a pop-p error message "Error: Forbi...on my Search tab https://www.beat-eu.org/platform/user/smarcel/?tab=searches
I am re-using a previous search by clicking to reach
https://www.beat-eu.org/platform/search/smarcel/MOBIO/
and I got a pop-p error message "Error: Forbidden" then loading forever.
Alternatively on my Search tab I am not able to create new Search anymore ?
Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/108Experiments panel at user micro-site is incomplete2015-04-14T09:32:00ZAndré AnjosExperiments panel at user micro-site is incompleteAfter the (very useful) mod to all visible objects displayed, there is a small issue concerning the experiment list: we cannot see who's the experiment owner. It would be good to add this field.
As a matter of fact, it would be better...After the (very useful) mod to all visible objects displayed, there is a small issue concerning the experiment list: we cannot see who's the experiment owner. It would be good to add this field.
As a matter of fact, it would be better to merge "Toolchain" and "Label" into a single heading (called "Label"), for which we print the whole experiment label (i.e. as returned by experiment.fullname()). That would be more consistent with the other panels.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/104Public algorithms are not being listed2015-04-10T10:08:24ZAndré AnjosPublic algorithms are not being listedIn the user microsite, the others' public algorithms available are not being displayed. Need a fix.In the user microsite, the others' public algorithms available are not being displayed. Need a fix.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/103The JS canvas of the toolchain editor stopped working2015-04-09T11:32:54ZAndré AnjosThe JS canvas of the toolchain editor stopped workingThe JS canvas of the JS editor stopped working after the last upgrade.
@philip.abbet: could you please take a look since you're our only expert on this component?The JS canvas of the JS editor stopped working after the last upgrade.
@philip.abbet: could you please take a look since you're our only expert on this component?Tutorial for the FG2015 ConferencePhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/105User w/o permissions can still access restricted queues2015-04-08T21:46:27ZAndré AnjosUser w/o permissions can still access restricted queuesFor example, the queue "Idiap Biometrics (Long)", should only be accessible to users of the "Idiap Biometrics" group, but are accessible to any user. Actually, there are no users on that group, so the queue should be accessible to none.For example, the queue "Idiap Biometrics (Long)", should only be accessible to users of the "Idiap Biometrics" group, but are accessible to any user. Actually, there are no users on that group, so the queue should be accessible to none.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/102"Send configuration to scheduler" button stopped working2015-04-08T20:00:54ZAndré Anjos"Send configuration to scheduler" button stopped workingAfter the latest upgrades, we can no longer send the configuration to the scheduler.
The reason is related:
```text
{"detail":"CSRF Failed: CSRF token missing or incorrect."}
```
A missing CSRF protection, likely, on the JS si...After the latest upgrades, we can no longer send the configuration to the scheduler.
The reason is related:
```text
{"detail":"CSRF Failed: CSRF token missing or incorrect."}
```
A missing CSRF protection, likely, on the JS side.
We must fix this ASAP.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/91DELETE action was removed from <base>/experiments/configuration/...2015-03-27T12:38:52ZAndré AnjosDELETE action was removed from <base>/experiments/configuration/...According to @samuel.gaist, this was done during the rest framework port. We should bring this API back.According to @samuel.gaist, this was done during the rest framework port. We should bring this API back.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/93Object list in the user micro-site does not include all visible contributions2015-03-27T12:38:43ZAndré AnjosObject list in the user micro-site does not include all visible contributionsWhen listing objects in the user micro-site, it would better if the user had access to all visible contributions, organized this way:
1. The user's own contributions
2. Objects which have been explicitly shared with the user
3. All ...When listing objects in the user micro-site, it would better if the user had access to all visible contributions, organized this way:
1. The user's own contributions
2. Objects which have been explicitly shared with the user
3. All other public contributions
The filtering bar on the top should work-out fine so that the user can fine-tune the results.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/94URL field "format=string" does not work after Django rest framework port2015-03-27T12:38:34ZAndré AnjosURL field "format=string" does not work after Django rest framework portThis field in the URL is used by the rest framework to define which serializer/marshaller to use.
We will need to change this everywhere to something like `object-format=string`.This field in the URL is used by the rest framework to define which serializer/marshaller to use.
We will need to change this everywhere to something like `object-format=string`.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/92Team creation form2015-03-27T12:37:48ZAndré AnjosTeam creation formThe team creation form is in place. A couple of fixes are due:
- [x] It would be good that we describe, somewhere, what the different privacy levels mean.
- [x] It would be better to have the whole form completable at once, in a sing...The team creation form is in place. A couple of fixes are due:
- [x] It would be good that we describe, somewhere, what the different privacy levels mean.
- [x] It would be better to have the whole form completable at once, in a single page, instead of creating the team and then editing its attributes
- [x] It would be good if, by clicking on the team (at the user micro-site), the system took the user to the team edition page as for other objects. Some harmonization should be put in place for this.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/84Synchronisation issue between the system status and the internal status ?2015-03-27T06:09:52ZSébastien MARCELSynchronisation issue between the system status and the internal status ?there might be a synchronisation issue between the system status ( https://www.beat-eu.org/platform/ ) and the internal status. Indeed, the status says that 1 experiment is running but clearly looking at the scheduler page this is not th...there might be a synchronisation issue between the system status ( https://www.beat-eu.org/platform/ ) and the internal status. Indeed, the status says that 1 experiment is running but clearly looking at the scheduler page this is not the case.
Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/14User grouping2015-03-27T06:02:04ZAndré AnjosUser groupingTracker for user grouping. Edit as we progress on the understanding of this feature.Tracker for user grouping. Edit as we progress on the understanding of this feature.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/44User secret keys are not verified2015-03-27T05:59:53ZAndré AnjosUser secret keys are not verifiedIt would be good that, at a certain point, the usage and definition of secret keys by users actually worked for authenticating users.
Today it is not the case.It would be good that, at a certain point, the usage and definition of secret keys by users actually worked for authenticating users.
Today it is not the case.Tutorial for the FG2015 ConferenceSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/7Improvements to the beat command-line tool (migrated from github)2015-03-25T07:37:09ZAndré AnjosImprovements to the beat command-line tool (migrated from github)- [x] Pull a configuration
- [x] Push a configuration
- [x] Edition/Pull/Push of descriptions associated to different objects
- [x] Color configuration
- [x] Check of a toolchain `beat toolchain check ...`
- [x] Algorithm changes de...- [x] Pull a configuration
- [x] Push a configuration
- [x] Edition/Pull/Push of descriptions associated to different objects
- [x] Color configuration
- [x] Check of a toolchain `beat toolchain check ...`
- [x] Algorithm changes detection when running an experiment
- [x] Check user existence in commands like: `beat algorithms pull --user ADHDAHGDGAHSGHDAGHSDGH`. Presently, this is silently ignored.
- [x] While running locally, it would be nice that this package printed out more information about data input and output. It is currently very summarized.
Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/4Changes to the TOS web site behavior2015-03-18T13:16:48ZAndré AnjosChanges to the TOS web site behaviorBased on discussions with our lawyers and legal partner (Els), I've updated the ToS documentation that is required for Users (i.e. people registering into the platform). Things to do:
1. [x] @Kanma: **URGENT**: Update the ToS using th...Based on discussions with our lawyers and legal partner (Els), I've updated the ToS documentation that is required for Users (i.e. people registering into the platform). Things to do:
1. [x] @Kanma: **URGENT**: Update the ToS using the new `tos.rst` in `docs`.
2. [x] In the ToS, a "Contact Form" is mentioned. This form should be used to notify Idiap of problems with the use or management of the BEAT platform. Currently, this contact form does not exist in our platform. It must be created (with a captcha to avoid spamming). Once that is established, one should replace the placeholder for the contact form in the ToS with the final address. Currently it is set to https://beat-eu.org/platform/contact
3. [x] In discussion with our lawyers, it became clear we need to establish a feature that identifies if a certain **Visitor** (this is != User) is a first time visitor or a recurrent visitor (possibly using cookies). If the visitor is a first time visitor, a banner should pop-up (discretely) and say: "The BEAT Platform, like other sites on the internet, uses cookies to customise your interaction with the platform itself. By visiting the IDIAP BEAT Platform you implicitly acknowledge our Legal Disclaimer." At this point, the words "Legal Disclaimer" should be clickable and point to the `legal_disclaimer.rst` file in the `docs` directory. The file should be displayed like the ToS, as a pop-up. *Users that dismiss the banner, get a cookie indicating they have accepted the disclaimer, with a given version number*.
4. [x] In the Legal Disclaimer, a link to the ToS should be made available. A place holder pointing to "https://beat-eu.org/platform/tos" is there, but should be updated if that changes. Action Point: We should create a URL that points to the ToS like stated.
5. [x] Both the "ToS" and our "Legal Disclaimer" have a version number. Users that access the platform **after** the ToS has been updated, should get a banner pointing to the new ToS. Visitors that access the platform **after** the "Legal Disclaimer" has been updated should also check it again. Note that **Users** don't need to go through the "Legal Disclaimer", just visitors. *This feature can be achieved by comparing the cookie established on the user browser with the current version of the ToS/Legal Disclaimer and showing/updating it*.
6. [x] While we can make sure that a person that does not accept the ToS cannot register, we cannot make sure that a Visitor that does not agree with the Legal Disclaimer will not continue visiting the website. By clicking on the "banner close" button or by popping up the "Legal Disclaimer", the user implicitly agrees with what is said in there. If they don't agree, then they should just leave the website. At this point, creating a mechanism to block the contents may be tricky (@Kanma: what do you think about this?)
After all these items have been implemented, I think we can finally close this issue.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/71Inserting an invalid JSON for a database generates a beat.web error2015-03-18T12:52:42ZAndré AnjosInserting an invalid JSON for a database generates a beat.web errorA simple test is to copy-paste the JSON containing version and short doc strings.A simple test is to copy-paste the JSON containing version and short doc strings.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/53Validation of all Contributions must be more thorough2015-03-18T12:17:09ZAndré AnjosValidation of all Contributions must be more thoroughCurrently, the validation of contributions saved on our database does not go through important accessibility check that must be executed before object insertion.
Namely, the following checks should be performed:
* [x] When the user...Currently, the validation of contributions saved on our database does not go through important accessibility check that must be executed before object insertion.
Namely, the following checks should be performed:
* [x] When the user inserts a data format, that all referenced data formats are accessible
* [x] When the user saves an algorithm that all referenced data formats are acessible
* [x] When the user saves an experiment, that databases, algorithms, analysers, data formats and environments are accessible.
When all these items are checked, we can safely close this bug.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/86Missing API for downloading databases and views2015-03-18T12:16:12ZAndré AnjosMissing API for downloading databases and viewsWe're currently missing an API to download databases (JSON and views) associated with experiments. There should be no reason why this should not be possible.
Currently, after downloading and experiment, the toolchain and related algor...We're currently missing an API to download databases (JSON and views) associated with experiments. There should be no reason why this should not be possible.
Currently, after downloading and experiment, the toolchain and related algorithms and dataformats, the user may not validate the experiment because it is lacking the database definition.
Clearly, we're not talking about the real data, just the (JSON and python views) associated with the platform. Confidentiality should be respected in all cases.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/15Consolidation of platform statistics2015-03-06T08:15:22ZAndré AnjosConsolidation of platform statisticsWe current have an initial implementation for the platform statistics. We need to improve on it so its useful for platform demonstrations and system administration.
It would be nice to integrate this with the new scheduler state as well.We current have an initial implementation for the platform statistics. We need to improve on it so its useful for platform demonstrations and system administration.
It would be nice to integrate this with the new scheduler state as well.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.core/-/issues/2Warning for unconnected/multiply connected blocks (migrated from github)2015-03-06T08:05:11ZAndré AnjosWarning for unconnected/multiply connected blocks (migrated from github)Along the same lines as #39, it would be convenient that both `check_toolchain.py` and `run_toolchain.py` would check for unconnected blocks and issue a **warning** in case one is detected. It would be an immense helper for debugging new...Along the same lines as #39, it would be convenient that both `check_toolchain.py` and `run_toolchain.py` would check for unconnected blocks and issue a **warning** in case one is detected. It would be an immense helper for debugging new toolchains.Tutorial for the FG2015 ConferenceAndré AnjosAndré Anjos