beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2018-01-11T16:16:25Zhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/1Toolchain editor2018-01-11T16:16:25ZJaden DIEFENBAUGHToolchain editorhttps://gitlab.idiap.ch/beat/beat.web/-/issues/478Bad handling of complex DOM ids using querySelector2017-11-14T13:51:14ZJaden DIEFENBAUGHBad handling of complex DOM ids using querySelectorUsing the statement:
```js
document.querySelector(`#${ id }`)
```
where `id` is a string representing a DOM id can only handle a certain subset of allowable id strings. For example, whitespace will break this, because `querySelector` par...Using the statement:
```js
document.querySelector(`#${ id }`)
```
where `id` is a string representing a DOM id can only handle a certain subset of allowable id strings. For example, whitespace will break this, because `querySelector` parses the given query string as a CSS query selector.
To fix, use `document.getElementById` for queries against element ids:
```js
document.getElementById(`${ id }`)
```Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.web/-/issues/477In the experiment list view, experiments that participate on Reports are not ...2017-09-28T08:42:03ZAndré AnjosIn the experiment list view, experiments that participate on Reports are not flaggedIn the experiments list view, we have an icon that indicates if an experiment has an associated attestation-lock or a public attestation. That gives the user a notion if the assets of the said experiment are locked (frozen).
Experiments...In the experiments list view, we have an icon that indicates if an experiment has an associated attestation-lock or a public attestation. That gives the user a notion if the assets of the said experiment are locked (frozen).
Experiments that participate in a report are also "locked" (frozen assets), but that information is not shared on the experiment list view. It would be nice if one could see this information as well.Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/476C++ environment has no documentation2017-09-28T08:43:21ZAndré AnjosC++ environment has no documentationThe current version of the C++ environment at the production platform has no associated documentation.
We should explain there what it is and maybe have links to the different software toolkits and instructions on how to produce a binar...The current version of the C++ environment at the production platform has no associated documentation.
We should explain there what it is and maybe have links to the different software toolkits and instructions on how to produce a binary that is compatible with it.Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/475New version or fork of algorithm with RST URL gets buggy documentation2017-09-27T14:52:17ZAndré AnjosNew version or fork of algorithm with RST URL gets buggy documentationIf you fork or copy an algorithm that has documentation in restructured text format containing an URL such as `My test <http://example.com>`, the copy or fork will end-up with `&lt;` and `&gt;` characters in the place of `<` and `>` and ...If you fork or copy an algorithm that has documentation in restructured text format containing an URL such as `My test <http://example.com>`, the copy or fork will end-up with `<` and `>` characters in the place of `<` and `>` and will produce an annoying warning.
Example: Try to fork `tutorial/dct/3` (https://www.beat-eu.org/platform/algorithms/tutorial/dct/3/), then, edit the fork documentation.Philip ABBETPhilip ABBEThttps://gitlab.idiap.ch/beat/beat.web/-/issues/474Instructions for publishing attestations not very clear2017-09-27T14:40:18ZJaden DIEFENBAUGHInstructions for publishing attestations not very clearHello,
I got an email from beat saying that the attestation of my experiment is about to expire.
"More details: http://www.beat-eu.org/platform/attestations/232222665/"
The message informs me that if I don't take any action, the attestat...Hello,
I got an email from beat saying that the attestation of my experiment is about to expire.
"More details: http://www.beat-eu.org/platform/attestations/232222665/"
The message informs me that if I don't take any action, the attestation will be deleted [soon].
But it does not tell me what actions I could take.
The link on the "more details" line takes me to the attestation of the experiment in question.
Here again, I see the following information at the beginning of the page:
"
Created 5 months, 3 weeks ago, Jan. 5, 2017, 5:28 p.m.
Expires in 5 days, 6 hours from now, on July 4, 2017, 5:28 p.m. (unlock it to make it permanent)
Experiment: sbhatta/ivana7c/simple-antispoofing-updated/1/replay2-antispoofing-lbp-histograms
Description: Face antispoofing using comparison of LBP histograms
"
The second line says "unlock it to make it permanent", but I could not understand what "unlock it" means.
Finally, someone explained to me that I have to click on the yellow-star-wheel to "Publish" it.
Overall, I found the instructions not very clear.
I would expect the text "unlock it to make it permanent" to be an active link, which would lead to
the appropriate action.
Regards
Sushilhttps://gitlab.idiap.ch/beat/beat.web/-/issues/473Add/merge userspace documentation for reports app changes2018-10-31T08:21:40ZJaden DIEFENBAUGHAdd/merge userspace documentation for reports app changesThe userspace documentation changes for the updates to the reports app didn't make it to staging...hopefully I have a stash/branch somewhere, but I'll probably need to rewrite it all.The userspace documentation changes for the updates to the reports app didn't make it to staging...hopefully I have a stash/branch somewhere, but I'll probably need to rewrite it all.Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/14More detailed logging at various verbosity levels2017-08-25T07:36:23ZJaden DIEFENBAUGHMore detailed logging at various verbosity levelsRight now, the various verbosity levels don't provide much more information than not passing a verbosity level at all. Some ideas:
- More cache information
- Logging the block & its cache would be especially useful
- More statistics (...Right now, the various verbosity levels don't provide much more information than not passing a verbosity level at all. Some ideas:
- More cache information
- Logging the block & its cache would be especially useful
- More statistics (especially for the local executor)
- Printing output of every block, not just the analyserhttps://gitlab.idiap.ch/beat/beat.web/-/issues/472Dependencies not being properly fetched in BEAT staging2017-08-31T12:37:56ZJaden DIEFENBAUGHDependencies not being properly fetched in BEAT stagingThe reports app is broken because it can't fetch two of the angular modules' dependencies:
- angular-ui-sortable
- angular-ui-codemirrorThe reports app is broken because it can't fetch two of the angular modules' dependencies:
- angular-ui-sortable
- angular-ui-codemirrorhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/12Add support for multiprocessing & multi environments2017-08-24T09:20:28ZJaden DIEFENBAUGHAdd support for multiprocessing & multi environmentsRe-add/enable support for `describe` from `beat.backend.python` in `beat.cmdline` for non-docker multi-environment support.Re-add/enable support for `describe` from `beat.backend.python` in `beat.cmdline` for non-docker multi-environment support.https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/11Add gridtk executor2017-08-24T08:42:54ZJaden DIEFENBAUGHAdd gridtk executorAdd another executor beside the Docker & local executors. This would also require refactoring the management of multiple executors.Add another executor beside the Docker & local executors. This would also require refactoring the management of multiple executors.https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/10Add cli options for overriding parameters2017-08-24T08:41:28ZJaden DIEFENBAUGHAdd cli options for overriding parametersFor example, to override the database `atnt/3`'s root folder, you could use the cli option `--database`:
```bash
./bin/beat exp run <example> --database='atnt/3=../atnt_db'
```
This could be expanded to experiment parameters (overriding...For example, to override the database `atnt/3`'s root folder, you could use the cli option `--database`:
```bash
./bin/beat exp run <example> --database='atnt/3=../atnt_db'
```
This could be expanded to experiment parameters (overriding values defined in experiment JSON files) by giving JSON objects. The following format could be used:
```bash
./bin/beat exp run <example> --override='"globals":{"user/pca/1":{"number-of-components": 20}}'
```https://gitlab.idiap.ch/beat/beat.web/-/issues/471Experiment quirk on production platform2017-06-30T12:42:25ZAndré AnjosExperiment quirk on production platformFor some reason this experiment was working before the update:
https://www.beat-eu.org/platform/experiments/anjos/tutorial/eigenface/1/atnt-eigenfaces-88-comp/
Now, if I fork it (change the number of components parameter to it does not...For some reason this experiment was working before the update:
https://www.beat-eu.org/platform/experiments/anjos/tutorial/eigenface/1/atnt-eigenfaces-88-comp/
Now, if I fork it (change the number of components parameter to it does not hit the cache), it cannot run anymore. E.g.:
https://www.beat-eu.org/platform/experiments/anjos/tutorial/eigenface/1/atnt-eigenfaces-120-comp-check/
The failed experiment complains about an error on the user side. Any suggestions?https://gitlab.idiap.ch/beat/beat.web/-/issues/470API requests to `/api/v1/plotters/plotterparameters/` return nothing conditio...2017-08-23T11:36:40ZJaden DIEFENBAUGHAPI requests to `/api/v1/plotters/plotterparameters/` return nothing conditionally##### What
Requesting the plotter parameters of the platform return an empty `[]` when requested by an anonymous user when the report is locked (EDIT: *or* if it's published).
##### Reproduce
- Create a new report and add experiment...##### What
Requesting the plotter parameters of the platform return an empty `[]` when requested by an anonymous user when the report is locked (EDIT: *or* if it's published).
##### Reproduce
- Create a new report and add experiments
- Add a plot
- Save report
- Lock report
- View the report/publication URL
- Look in the network activity panel of your browser's devtools, find the request for the plotterparameters
- **Since you are logged in, it correctly has fetched the plotter parameters**
- Copy report publication URL
- Log out
- View report publication URL
- Look at the network panel again and find the request
- **Expected: The plotterparameters are returned**
- **Actual: An empty `[]` is returned**https://gitlab.idiap.ch/beat/beat.web/-/issues/469Upgrade angular dependency (and possibly others as well)2018-10-31T08:20:05ZJaden DIEFENBAUGHUpgrade angular dependency (and possibly others as well)Beyond maintainence (see Angular's [changelog](https://github.com/angular/angular.js/blob/master/CHANGELOG.md) which has hundreds of bug fixes since 1.4.5), there's a few reasons I'd like to upgrade (in order of concreteness):
1. Custom ...Beyond maintainence (see Angular's [changelog](https://github.com/angular/angular.js/blob/master/CHANGELOG.md) which has hundreds of bug fixes since 1.4.5), there's a few reasons I'd like to upgrade (in order of concreteness):
1. Custom comparators for ordering elements (e.g. multi-column sorting, see jdiefenbaugh/beat.web#22)
2. Performance improvements which would help smooth the UX
3. Lets us upgrade jQuery to v3
4. (ties in with 3) lets us track the current development/maintenance of Angular 1 & its ecosystem
As far as breaking changes go - there's not much, since we're just using standard Angular features:
1. There might be an issue with [`$sce`](https://docs.angularjs.org/api/ng/service/$sce), Angular's utility for sanitizing strings before using them in things like resource URLs or dynamically-compiled HTML. Angular may require using `$sce` more often in our code, if we use complex `$compile` calls or use dynamic resource `href`s in our templates.
2. Angular's custom `success` and `error` methods for calls to `$http` have been deprecated and then removed. They now recommend using the official JS solution, `then` and `catch`, which have huge browser support & more features. There aren't many instances we need to change, either. A quick grep shows:
```
beat/web/ui/static/ui/js/reportdialog.js
153: .success(function (reportData)
160: .error(function (error)
250: .success(function (reportData)
257: .error(function (error)
273: .success(function (reportData)
280: .error(function (error)
394: .success(function (reportData)
401: .error(function (error)
beat/web/plotters/static/plotters/app/controllers/plotterparameterController.js
64: .success(function (plottersData)
72: .error(function (error)
83: .success(function (plotterparameterData)
124: .error(function (error)
beat/web/plotters/static/plotters/app/directives/plotterparameterItemView.js
201: .success(function (returnedData)
207: .error(function (error)
252: .success(function (returnedData)
257: .error(function (error)
314: .success(function (returnedData)
319: .error(function (error)
381: .success(function (returnedData)
386: .error(function (error)
beat/web/reports/static/reports/app/directives/saveReportItems.js
35: .error(function (error){
```2017-05-19https://gitlab.idiap.ch/beat/beat.web/-/issues/468Merge button not shown in bar plots2017-08-23T11:36:42ZJaden DIEFENBAUGHMerge button not shown in bar plotsSee jdiefenbaugh/beat.web#17 for background info.
Should the merge button be shown for bar plots? If so, this is a bug.See jdiefenbaugh/beat.web#17 for background info.
Should the merge button be shown for bar plots? If so, this is a bug.https://gitlab.idiap.ch/beat/beat.web/-/issues/467Possibly no plotterparameters for bar plots2017-08-06T16:44:51ZJaden DIEFENBAUGHPossibly no plotterparameters for bar plotsSee jdiefenbaugh/beat.web#19 and jdiefenbaugh/beat.web#17 for some background info if needed.See jdiefenbaugh/beat.web#19 and jdiefenbaugh/beat.web#17 for some background info if needed.https://gitlab.idiap.ch/beat/beat.web/-/issues/466Scatter plot entries in database not correct2018-10-31T08:23:14ZJaden DIEFENBAUGHScatter plot entries in database not correctSee jdiefenbaugh/beat.web#16 for how we figured this out.
The scatter plot entry in `plotter_plotterparameter` has its `sharing` column incorrectly set to `P` (Private), not `A` (All). This breaks the scatter plot capability for the pla...See jdiefenbaugh/beat.web#16 for how we figured this out.
The scatter plot entry in `plotter_plotterparameter` has its `sharing` column incorrectly set to `P` (Private), not `A` (All). This breaks the scatter plot capability for the platform.https://gitlab.idiap.ch/beat/beat.web/-/issues/465Selecting different options in modal breaks select box2017-08-23T11:36:36ZJaden DIEFENBAUGHSelecting different options in modal breaks select box(See jdiefenbaugh/beat.web#13)
When adding experiments to a report, you are asked to select which report to try to add the experiments to. The first time you select any available report, the report name correctly shows as the "selected"...(See jdiefenbaugh/beat.web#13)
When adding experiments to a report, you are asked to select which report to try to add the experiments to. The first time you select any available report, the report name correctly shows as the "selected" value. However, after a few times of choosing different reports, the selected report name is pushed to the far right, and you can't read it.
Just by playing around in the browser's inspect mode, I was able to fix this issue by changing the raw HTML. Changing the HTML element that contains the selected report name from a `div` to a `span` corrects this - I'm guessing it's because `div`s are not inline by default, while `span`s are.https://gitlab.idiap.ch/beat/beat.web/-/issues/464Chrome headless for more stable & CI-supported E2E testing2017-08-06T16:44:50ZJaden DIEFENBAUGHChrome headless for more stable & CI-supported E2E testingE2E testing currently uses a locally-installed browser and cannot be ran on a headless CI. Using a locally-installed browser is:
1. annoying
2. resource-intensive
3. not feasible on CI
Chrome has recently started to support running the ...E2E testing currently uses a locally-installed browser and cannot be ran on a headless CI. Using a locally-installed browser is:
1. annoying
2. resource-intensive
3. not feasible on CI
Chrome has recently started to support running the browser headlessly, which will fix these issues. However, it's not very well supported yet (still Alpha~Beta stage). This is a tracking issue for widespread support.
See:
- https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md
- https://www.chromestatus.com/feature/5678767817097216