beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2015-08-28T12:46:10Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/253Long description field gets mangled symbols2015-08-28T12:46:10ZAndré AnjosLong description field gets mangled symbolsFor some reason, when the platform copies the object description to the edit box (restructuredtext), symbols like ``<`` (typically used inside URLs in restructuredtext) gets translated to ``&lt;`` and is displayed as such. If the user tr...For some reason, when the platform copies the object description to the edit box (restructuredtext), symbols like ``<`` (typically used inside URLs in restructuredtext) gets translated to ``<`` and is displayed as such. If the user tries to save the text, he/she will get an error in a place typically unrelated to the change.
How to reproduce this problem:
1. At http://beatweb-staging, fork the algorithm ``tutorial/linear_machine_projection/5``
2. Scroll down as to edit its documentation. It shows:
```text
The linear transformation relies on the `Bob <http://www.idiap.ch/software/bob>`_ library (version 2).
```
Whereas it should show:
```text
The linear transformation relies on the `Bob <http://www.idiap.ch/software/bob>`_ library (version 2).
```
I guess we're escaping too much somewhere.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/272[reports] missing ability to delete report items2015-08-27T14:43:53ZFlavio TARSETTI[reports] missing ability to delete report itemsHaving the possibilty to delete a table or plot would be goodHaving the possibilty to delete a table or plot would be goodBTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/245[reports] Sharing/locking behaviour2015-08-27T14:43:51ZAndré Anjos[reports] Sharing/locking behaviourHow can one show a report to somebody else not sitting immediately by his side? Despite the fact other objects are shareable at the platform, reports and attestations need to be locked before they can be shared. I wonder what would be th...How can one show a report to somebody else not sitting immediately by his side? Despite the fact other objects are shareable at the platform, reports and attestations need to be locked before they can be shared. I wonder what would be the workflow to collaboratively create a report or (on a minor scale) an attestation.
Differently than attestations, reports combine displaying features that authors (working remotely) may need to agree while composing an article. IMO, being able to share a report sounds like a good idea.
Attestations don't suffer from this problem because, if you lock them, other people can see it. Reports, on the other end, can only be seen while locked so the user would have to:
1. Lock report
2. Share link with remote party
3. If comments from remote party: unlock report (now not visible anymore to remote party)
4. Modify the report and go back to 1 as many times as necessary
This looks a bit cumbersome - would you agree? In this context, would it make sense to have reports a subclass of "Shareable" as suggested on one of our discussions?BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/258[reports] "Add to report" button on freshly finished experiments is grayed-out2015-08-27T14:43:50ZAndré Anjos[reports] "Add to report" button on freshly finished experiments is grayed-outI guess it is just missing a "refresh" after the experiment is finished.
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/552128c7a240269eeb67ac23e8d2c065/image.png)
I guess it is just missing a "refresh" after the experiment is finished.
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/552128c7a240269eeb67ac23e8d2c065/image.png)
BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/269[reports] No way to remove an experiment from a report2015-08-27T14:43:49ZAndré Anjos[reports] No way to remove an experiment from a reportThis was originally reported by @tiago.pereira on a mail to beat-devel, but that is really necessary. Since we're not dealing with a search here, but with an add-as-you-go system, being able to remove something wrongly inserted is a must.This was originally reported by @tiago.pereira on a mail to beat-devel, but that is really necessary. Since we're not dealing with a search here, but with an add-as-you-go system, being able to remove something wrongly inserted is a must.BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/185Reports: Locked & published report page2015-08-27T14:43:48ZPhilip ABBETReports: Locked & published report pageDepends on #184
The user should receive an unique link that allows a reviewer
to verify the table/figure (such as it works for individual experiment
Attestations).Depends on #184
The user should receive an unique link that allows a reviewer
to verify the table/figure (such as it works for individual experiment
Attestations).BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/273500 error when accessing queue permissions2015-08-27T14:43:10ZAndré Anjos500 error when accessing queue permissionsJust hit: http://beatweb-staging/admin/backend/queue/5/permissions/Just hit: http://beatweb-staging/admin/backend/queue/5/permissions/BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/241[reports] Cannot have spaces on their name, but no validation takes place2015-08-26T15:02:17ZAndré Anjos[reports] Cannot have spaces on their name, but no validation takes placeNo validation (through the admin panel) takes place for the "name" field on a report. The end result is administrators can type anything which will translate to a Django error when displaying the report page.
How to reproduce it:
1...No validation (through the admin panel) takes place for the "name" field on a report. The end result is administrators can type anything which will translate to a Django error when displaying the report page.
How to reproduce it:
1. Create a report through the admin site with spaces on its name
2. On the user site search for this report and click on it
Results: Django exception being thrown
Expected result: Either finds the page or has validation implemented so that names with spaces are not allowed.
Note: There is no good reason why reports with spaces should not be allowed. Or is there?BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/257[experiments] Long name for experiment causes an error2015-08-25T12:36:53ZAndré Anjos[experiments] Long name for experiment causes an errorIf a name with more than 100 characters is chosen for an experiment (using the experiment configuration), the platform shows a pop-up window with some sort of Python exception that is not digestable by the end-user:
![image](https://g...If a name with more than 100 characters is chosen for an experiment (using the experiment configuration), the platform shows a pop-up window with some sort of Python exception that is not digestable by the end-user:
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/3a4b7850786d378b0e34de66de5069db/image.png)
Ideally, it should point out the problem and let the user choose another name.
This is probably related to the latest ``label`` -> ``name`` changes on experiments.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/270[reports] Cannot cooperatively create a report2015-08-21T15:19:25ZAndré Anjos[reports] Cannot cooperatively create a reportBecause reports can't be shared today, it is not possible to write a joint publication using the platform w/o a very cumbersome workflow. Like searches, reports should also be shareable.
What would take it for this to be done?Because reports can't be shared today, it is not possible to write a joint publication using the platform w/o a very cumbersome workflow. Like searches, reports should also be shareable.
What would take it for this to be done?BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/266[attestations] Migration is not setting a proper expiration date on existing ...2015-08-21T00:57:42ZAndré Anjos[attestations] Migration is not setting a proper expiration date on existing attestationsWe should implement this as a migration, otherwise existing attestations will never expire.We should implement this as a migration, otherwise existing attestations will never expire.BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/267[api docs] Attestation API is bogus2015-08-21T00:57:41ZAndré Anjos[api docs] Attestation API is bogusI'm now getting this from rest-swagger. Clues?
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/4ee43fecf19c8beaae6c573714536a9a/image.png)
I'm now getting this from rest-swagger. Clues?
![image](https://gitlab.idiap.ch/biometric/beat.web/uploads/4ee43fecf19c8beaae6c573714536a9a/image.png)
BTAS TutorialSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/265[reports] Not being properly backed-up2015-08-20T15:54:14ZAndré Anjos[reports] Not being properly backed-upAs of today, the reports app is not working well (meaning it does not backup anything) with our custom backup command. We need to fix this ASAP.As of today, the reports app is not working well (meaning it does not backup anything) with our custom backup command. We need to fix this ASAP.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/264[plotters] Default plotter for plot/scatter/1 is generating a 500 error2015-08-20T10:25:21ZAndré Anjos[plotters] Default plotter for plot/scatter/1 is generating a 500 errorSomething changed since our last update. Needs to be checked as soon as possible.Something changed since our last update. Needs to be checked as soon as possible.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/255[backend] Queue-less environments should not be displayed at experiment confi...2015-08-19T21:04:19ZAndré Anjos[backend] Queue-less environments should not be displayed at experiment configuratorAs of today, the experiment configuration is displaying environments for selection that correspond to no configured queue. This generates a awkward situation for the user. Must be fixed as soon as possible.As of today, the experiment configuration is displaying environments for selection that correspond to no configured queue. This generates a awkward situation for the user. Must be fixed as soon as possible.BTAS TutorialAndré AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.web/-/issues/262[experiments] default plotter is not selected and missing plotter parameter2015-08-19T12:51:08ZFlavio TARSETTI[experiments] default plotter is not selected and missing plotter parameterBTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/252[reports] When saving a report, a confirmation would be handy2015-08-19T12:51:07ZAndré Anjos[reports] When saving a report, a confirmation would be handyCurrently, when saving a report, the user has no confirmation on the fact the report was saved (or not). It would be useful to have some sort of confirmation about the operation.Currently, when saving a report, the user has no confirmation on the fact the report was saved (or not). It would be useful to have some sort of confirmation about the operation.BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/251[reports] When adding a plot item on a report, cannot select "parameters"2015-08-19T12:51:07ZAndré Anjos[reports] When adding a plot item on a report, cannot select "parameters"The selector only appears after I first save the report (once I added the plot item).The selector only appears after I first save the report (once I added the plot item).BTAS TutorialFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.web/-/issues/261[algorithms] Save button not working on master2015-08-19T07:50:38ZAndré Anjos[algorithms] Save button not working on masterHello, I'm getting the following JS error when pressing the "Save" button after forking an algorithm. The button seems to work on the staging system, but not on my local checkout of the master HEAD.
How to reproduce it:
1. Fork an ...Hello, I'm getting the following JS error when pressing the "Save" button after forking an algorithm. The button seems to work on the staging system, but not on my local checkout of the master HEAD.
How to reproduce it:
1. Fork an algorithm
2. Set a name
3. Click on the save button
The save button has no effect. Looking at the error console, I get the following:
![Screen_Shot_2015-08-19_at_09.02.44](https://gitlab.idiap.ch/biometric/beat.web/uploads/830cd6b0146c38042f845ddf71c74547/Screen_Shot_2015-08-19_at_09.02.44.png)
My version of Safari (on OS X 10.10.4):
![Screen_Shot_2015-08-19_at_09.03.15](https://gitlab.idiap.ch/biometric/beat.web/uploads/b17c23b54c156ab5ab6abad798e83e86/Screen_Shot_2015-08-19_at_09.03.15.png)
BTAS TutorialPhilip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/8Deletion of objects by the user2015-08-19T07:50:38ZAndré AnjosDeletion of objects by the userUsers need to be able to delete (private) objects using the web interface. So far, this is only possible through the command-line. The following objects should be deletable:
- [x] experiments, if not certified (public or private, w/o ...Users need to be able to delete (private) objects using the web interface. So far, this is only possible through the command-line. The following objects should be deletable:
- [x] experiments, if not certified (public or private, w/o distinction)
- [x] toolchains, if not used on any experiment. If so, then the experiments must be deleted before the toolchain becomes deletable. I'm not sure what to do with the forking status of forked toolchains.
- [x] algorithms, if not used on any experiment. If so, follow the same rules as for toolchains.
- [x] dataformats, the same as for toolchains and algorithmsBTAS TutorialPhilip ABBETPhilip ABBET