beat issues
https://gitlab.idiap.ch/groups/beat/-/issues
2015-07-21T10:31:29Z
https://gitlab.idiap.ch/beat/beat.web/-/issues/196
Django-rest-swagger uses http scheme instead of https
2015-07-21T10:31:29Z
Laurent EL SHAFEY
Django-rest-swagger uses http scheme instead of https
On the production platform, the API documentation is available [here](https://www.beat-eu.org/platform/docs/). However, there is an issue with django-rest-swagger.
When clicking on the above mentioned documentation link, the address h...
On the production platform, the API documentation is available [here](https://www.beat-eu.org/platform/docs/). However, there is an issue with django-rest-swagger.
When clicking on the above mentioned documentation link, the address http://www.beat-eu.org/platform/docs/api-docs/ is shown instead of https://www.beat-eu.org/platform/docs/api-docs/, and the API documentation is not shown. If we manually update this address (to use https), then the API documentation shows up.
The suggestion of [this issue](https://github.com/marcgibbons/django-rest-swagger/issues/220) is already applied in the Django's settings.py of the production server and this does not help.
Debugging at the javascript level, swagger submits a request with ``scheme`` set to ``http`` instead of ``https``. Unfortunately, I've not found any way to force the use of `https` in django-rest-swagger.
https://gitlab.idiap.ch/beat/beat.web/-/issues/195
Experiment forking does not work anymore
2015-06-02T13:49:13Z
Laurent EL SHAFEY
Experiment forking does not work anymore
When forking an experiment, we end up on the experiment setup page with the correct toolchain. However, algorithm (inclusive parameters) and datasets are both missing.
When forking an experiment, we end up on the experiment setup page with the correct toolchain. However, algorithm (inclusive parameters) and datasets are both missing.
BEAT Tour
https://gitlab.idiap.ch/beat/beat.web/-/issues/194
Experiment API does not return anything when field 'sharing' is provided
2015-06-02T13:49:13Z
Laurent EL SHAFEY
Experiment API does not return anything when field 'sharing' is provided
When performing a query such as:
GET api/v1/experiments/<experiment-fullname>/?fields=sharing
it currently does not return anything.
Since such a construction is used to display experimental results, this makes impossible to display...
When performing a query such as:
GET api/v1/experiments/<experiment-fullname>/?fields=sharing
it currently does not return anything.
Since such a construction is used to display experimental results, this makes impossible to display the results of a private experiment. Looking at the code, this is related to the serializers (-> @samuel.gaist ).
BEAT Tour
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/193
Use Swagger for ReSTful API
2015-06-01T07:38:52Z
André Anjos
Use Swagger for ReSTful API
With the BEAT deliverables out of the way, it would be nice to think about a longer term documentation strategy for our web APIs. Now everything (please correct me if I'm wrong) uses Django's rest framework, it would be good to go for Sw...
With the BEAT deliverables out of the way, it would be nice to think about a longer term documentation strategy for our web APIs. Now everything (please correct me if I'm wrong) uses Django's rest framework, it would be good to go for Swagger. It is, at least, the recommendation from that library: http://www.django-rest-framework.org/topics/documenting-your-api/
BEAT Tour
https://gitlab.idiap.ch/beat/beat.web/-/issues/192
Cache clean-up operation not working anymore
2015-05-29T09:21:05Z
Laurent EL SHAFEY
Cache clean-up operation not working anymore
The cache clean-up operation is not working anymore. The guilty piece of code is:
``` js
if ($('#cache_cleanup_details input[name=mode]:checked')[0].value == '1')
```
in `beat/web/backend/templates/backend/scheduler.html` around line...
The cache clean-up operation is not working anymore. The guilty piece of code is:
``` js
if ($('#cache_cleanup_details input[name=mode]:checked')[0].value == '1')
```
in `beat/web/backend/templates/backend/scheduler.html` around line 728.
It is complaining as follows:
```
Uncaught TypeError: Cannot read property 'value' of undefined
```
I guess there is a problem with a template.
API Documentation
https://gitlab.idiap.ch/beat/beat.web/-/issues/191
Unlocking attestation does not work anymore
2015-05-28T10:28:47Z
Laurent EL SHAFEY
Unlocking attestation does not work anymore
The "unlock the attestation" button the attestation page does not work anymore.
The generated HTML is not valid and causes a `syntax error: unexpected string`.
It seems that there is a missing ',' after the attestation api_url (see b...
The "unlock the attestation" button the attestation page does not work anymore.
The generated HTML is not valid and causes a `syntax error: unexpected string`.
It seems that there is a missing ',' after the attestation api_url (see below).
```
$('a#unlock_attestation').click(function() {
beat.attestations.dialogs.Unlocking('unlock',
'user',
'/api/v1/attestations/unlock/2004723460/'
'/',
['system/integer/1'],
toolchain_viewer.configuration,
function()
{
window.location.reload();
}
);
```
API Documentation
https://gitlab.idiap.ch/beat/beat.web/-/issues/190
Experiment calling wrong API for block-finished
2015-05-28T10:11:16Z
Laurent EL SHAFEY
Experiment calling wrong API for block-finished
When running an experiment, a call to block-finished may happen. However, this is not using the right API, prefixed with V1, but `api/backend/block-finished/` instead.
When running an experiment, a call to block-finished may happen. However, this is not using the right API, prefixed with V1, but `api/backend/block-finished/` instead.
API Documentation
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/189
Toolchain editor is not working anymore
2015-05-28T07:20:18Z
Laurent EL SHAFEY
Toolchain editor is not working anymore
While trying to create a new toolchain with the editor on `master`, I'm getting the following error, which prevents me to reach the editor:
```
Uncaught SyntaxError: Unexpected identifier
(index):446 Uncaught ReferenceError: setupEd...
While trying to create a new toolchain with the editor on `master`, I'm getting the following error, which prevents me to reach the editor:
```
Uncaught SyntaxError: Unexpected identifier
(index):446 Uncaught ReferenceError: setupEditor is not defined
```
I'm unsure, which changes are at the origin of this problem.
API Documentation
https://gitlab.idiap.ch/beat/beat.web/-/issues/188
Web API for data format creation is inconsistent
2015-05-28T06:58:05Z
Laurent EL SHAFEY
Web API for data format creation is inconsistent
When I create a new dataformat, it does a POST request at the following address PLATFORM_URL/dataformats/new/.
In contrast and similarly to the other contributions, I would expect something like PLATFORM_URL/api/v1/dataformats/.
When I create a new dataformat, it does a POST request at the following address PLATFORM_URL/dataformats/new/.
In contrast and similarly to the other contributions, I would expect something like PLATFORM_URL/api/v1/dataformats/.
API Documentation
https://gitlab.idiap.ch/beat/beat.web/-/issues/187
team creation is not api v1 compatible
2015-05-27T15:23:25Z
Laurent EL SHAFEY
team creation is not api v1 compatible
While defining the API v1, it seems that the team creation has been forgotten.
If I try to create a team, I end up with such an error:
```
Page not found (404)
Request Method:
POST
Request URL:
http://127.0.0.1:8000/api/teams...
While defining the API v1, it seems that the team creation has been forgotten.
If I try to create a team, I end up with such an error:
```
Page not found (404)
Request Method:
POST
Request URL:
http://127.0.0.1:8000/api/teams/user/
Using the URLconf defined in beat.web.urls,
Django tried these URL patterns, in this order:
^$
[name='index']
^login/$
[name='login']
^user/(?P<username>\w+)/$
[name='userpage']
^settings/$
[name='user-settings']
^search/(?P<username>\w+)/(?P<queryname>[\w\-]+)/$
[name='search']
^search/$
[name='search']
^tos/$
[name='terms-of-service']
^disclaimer/$
[name='legal-disclaimer']
^contact/$
[name='contact']
^logout/$
[name='logout']
^signup/$
[name='registration']
^signup/complete/$
[name='registration-complete']
^signup/activate/(?P<activation_key>\w+)/$
[name='registration-activation']
^preregister/$
[name='pre-registration']
^preregistration/complete/$
[name='pre-registration-complete']
^algorithms/
^libraries/
^attestations/
^backend/
^dataformats/
^databases/
^experiments/
^statistics/
^toolchains/
^teams/
^plotters/
^admin/
^api/v1/teams/
^api/v1/algorithms/
^api/v1/attestations/
^api/v1/backend/
^api/v1/databases/
^api/v1/dataformats/
^api/v1/experiments/
^api/v1/libraries/
^api/v1/statistics/
^api/v1/toolchains/
^api/v1/plotters/
^api/v1/
^static\/(?P<path>.*)$
The current URL, api/teams/user/, didn't match any of these.
```
I guess that fixing the URL in the form should be enough.
Samuel GAIST
Samuel GAIST
https://gitlab.idiap.ch/beat/beat.web/-/issues/186
Reports: Export to CSV, LaTeX, PNG
2015-10-26T08:34:28Z
Philip ABBET
Reports: Export to CSV, LaTeX, PNG
Depends on #185
In a Locked Report, the table generated should be exportable in LaTeX or CSV mode, so that a user can adapt it to its own publication.
At minimum: CSV + PNG
Depends on #185
In a Locked Report, the table generated should be exportable in LaTeX or CSV mode, so that a user can adapt it to its own publication.
At minimum: CSV + PNG
Final Documentation
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.web/-/issues/185
Reports: Locked & published report page
2015-08-27T14:43:48Z
Philip ABBET
Reports: Locked & published report page
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).
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 Tutorial
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.web/-/issues/184
Reports: Report page editor
2015-10-02T15:47:34Z
Philip ABBET
Reports: Report page editor
Depends on #183
The Report page should allow the user to display features of the
experiment. Preferably, it should be made flexible enough so that new
conditions can be added in a relatively easy way (i.e., w/o necessarily
requiring a ...
Depends on #183
The Report page should allow the user to display features of the
experiment. Preferably, it should be made flexible enough so that new
conditions can be added in a relatively easy way (i.e., w/o necessarily
requiring a modification of large parts of the system). At first, apart
from what is already displayable at Search results, these are the other
conditions we'd thought are necessary. We've organized it in "Columns" of
interest, which can be mixed and matched upon user configuration.
- [x] Column "block computing time": Displays the computing time of a given block. Requires all experiments have a block with a given name
- [x] Column "total experiment time": Displays the total computing time for an experiment
- [x] Column "parameter value": Displays a parameter value in an algorithm for all experiments. Requires all experiments have an algorithm with a given value. If the algorithm has two values, displays a comma-separated list of values for each of those parameters.
- [x] Column "results": Displays any valid analyzer result.
- [x] Column "user label": Allows the user to define a label of its own for a given experiment.
Final Documentation
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.web/-/issues/183
Reports: Addition of experiments in a report from "anywhere"
2015-08-13T15:34:01Z
Philip ABBET
Reports: Addition of experiments in a report from "anywhere"
Depends on #181
On each relevant pages (experiment view, experiments list, search results), there should
be a button that allows to add the (selected) experiments into an existing (non-locked)
report, using the following process:
...
Depends on #181
On each relevant pages (experiment view, experiments list, search results), there should
be a button that allows to add the (selected) experiments into an existing (non-locked)
report, using the following process:
1. Display a list of the editable reports of the user + a *create new report* entry
2. Add the experiments to the selected report
3. If necessary, display back to the user the list of experiments that weren't added
to the report due to compatibility issue
BTAS Tutorial
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.web/-/issues/182
Reports: Add a reports tab on the user page
2015-06-02T09:58:17Z
Philip ABBET
Reports: Add a reports tab on the user page
Depends on #181
Similar to the *Attestations* one, with a *New* button
Depends on #181
Similar to the *Attestations* one, with a *New* button
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.web/-/issues/181
Reports: Model creation + Web API
2015-06-02T09:58:11Z
Philip ABBET
Reports: Model creation + Web API
**About the model:**
- A set of hand-picked experiments
- An author
- A name
- A documentation
- A unique number (see attestations)
- Must lock (not ```modifiable()``` nor ```deletable()```) experiments assigned to it
- Three po...
**About the model:**
- A set of hand-picked experiments
- An author
- A name
- A documentation
- A unique number (see attestations)
- Must lock (not ```modifiable()``` nor ```deletable()```) experiments assigned to it
- Three possible states: edition, locked, published
- The content of the report is defined using a JSON array (stored in the database),
where each entry might represent either a table (which columns + how to sort the
experiments + an optional caption) or a figure (whatever is needed to plot it +
an optional caption)
**Web API:**
* [x] creation of a report
* [x] deletion of a report
* [x] retrieval of a report
* [x] retrieval of a list of reports
* [x] locking of a report
* [x] publication of a locked report
* [x] addition of experiments in a report
* [x] removal of experiments from a report
* [x] update of the content of a report
Each endpoint must be tested.
Flavio TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.web/-/issues/180
Search: More flexible filters specification
2015-11-20T11:33:46Z
Philip ABBET
Search: More flexible filters specification
At the Search page, it would be good to be able to add logical-OR conditionals. Grouping of ANDs and ORs would be a plus.
**The report feature could be seen has a workaround for this feature!**
At the Search page, it would be good to be able to add logical-OR conditionals. Grouping of ANDs and ORs would be a plus.
**The report feature could be seen has a workaround for this feature!**
Final Documentation
Philip ABBET
Philip ABBET
https://gitlab.idiap.ch/beat/beat.web/-/issues/179
Search: Display multiple tables for experiments with multiple analyzers
2015-06-16T13:44:36Z
Philip ABBET
Search: Display multiple tables for experiments with multiple analyzers
Depends on #178
Depends on #178
BTAS Tutorial
Philip ABBET
Philip ABBET
https://gitlab.idiap.ch/beat/beat.web/-/issues/178
Search: Column sorting and reordering directly from the table header
2019-07-04T08:37:03Z
Philip ABBET
Search: Column sorting and reordering directly from the table header
With support for multi-column reordering.
Include a replacement of the custom SQL part by a more flexible Javascript implementation.
With support for multi-column reordering.
Include a replacement of the custom SQL part by a more flexible Javascript implementation.
Philip ABBET
Philip ABBET
https://gitlab.idiap.ch/beat/beat.web/-/issues/177
Search: Add one filter: algorithm in a given block
2019-07-04T08:37:03Z
Philip ABBET
Search: Add one filter: algorithm in a given block
Philip ABBET
Philip ABBET