beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2019-02-19T10:40:06Zhttps://gitlab.idiap.ch/beat/beat.core/-/issues/63`scripts/before_test.sh` has functionality that is required beyond this package2019-02-19T10:40:06ZAndré Anjos`scripts/before_test.sh` has functionality that is required beyond this packageThis script is responsible for 2 actions:
- pulling images for running tests
- ~~compiling c++-backend algorithms for testing~~
An equivalent script exists in beat.cmdline. This script is also called inside beat.web.
To align with a ...This script is responsible for 2 actions:
- pulling images for running tests
- ~~compiling c++-backend algorithms for testing~~
An equivalent script exists in beat.cmdline. This script is also called inside beat.web.
To align with a better DRY policy, the functionality of this script should be python-ified and provided as a service to callers. This problem relates to having a saner implementation beat/beat.web#510.
At this point, it may be desirable to update docker-py and related dependencies on our CI.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/510Improve CI to use conda-packages and python 3.62018-12-20T17:32:31ZAndré AnjosImprove CI to use conda-packages and python 3.6Our CI infrastructure for this package still uses Python 2.7!
A list of points we should consider when upgrading this:
- [x] Python 3.6
- [x] Use the latest beat-devel to install things like sphinx, nose, coverage and other required ba...Our CI infrastructure for this package still uses Python 2.7!
A list of points we should consider when upgrading this:
- [x] Python 3.6
- [x] Use the latest beat-devel to install things like sphinx, nose, coverage and other required base infrastructure
- [x] Install beat.cmdline, core and backend.python from our conda channel (beta) - if that is not possible, ensure this package only tests against the "master" branches of each of those
- [x] Reduce specific package pinning to the minimal required
- [x] buildout phase should not install anything - the file `dev.yml` should contain all dependencies - except, perhaps, the javascript stuff
- [x] the scripts to build .so files on beat.core is being called from this package - maybe we should consider to distribute pre-built binaries with beat.core for such a purpose? In particular, inside `buildout.cfg` we call these - need to figure out a solution...https://gitlab.idiap.ch/beat/beat.editor/-/issues/172CI broken - "npm not found"2018-12-06T10:24:07ZJaden DIEFENBAUGHCI broken - "npm not found"See https://gitlab.idiap.ch/beat/beat.editor/-/jobs/152718, specifically the line:
```
/local/builds/beat/beat.editor/miniconda/conda-bld/beat.editor_1543860509476/work/conda_build.sh: line 5: npm: command not found
```
This is in the ...See https://gitlab.idiap.ch/beat/beat.editor/-/jobs/152718, specifically the line:
```
/local/builds/beat/beat.editor/miniconda/conda-bld/beat.editor_1543860509476/work/conda_build.sh: line 5: npm: command not found
```
This is in the build step, so it doesn't concern the testing docker image.https://gitlab.idiap.ch/beat/beat.web/-/issues/508Password reset is not implemented2019-03-20T10:49:08ZAndré AnjosPassword reset is not implementedCurrently, there exists no way to recover the password from the platform. This is an important feature we need to implement.Currently, there exists no way to recover the password from the platform. This is an important feature we need to implement.https://gitlab.idiap.ch/beat/beat.web/-/issues/507The documentation is not backed up like other beat packages2018-12-18T07:06:07ZZohreh MOSTAANIThe documentation is not backed up like other beat packagesThe documentation for other beat packages are automatically backed up on https://www.idiap.ch/software/beat//docs/beat/ except for beat.web. This will be problematic since I am going to change the documentation of beat platform.The documentation for other beat packages are automatically backed up on https://www.idiap.ch/software/beat//docs/beat/ except for beat.web. This will be problematic since I am going to change the documentation of beat platform.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/171beat editor does not accept api version 2 as valid2018-11-27T11:19:24ZZohreh MOSTAANIbeat editor does not accept api version 2 as validI am trying to test algorithms written with api version 2 that is introduced in the new platform release. beat editor shows them as invalid all the time. The experiments are running and the algorithms are correct.I am trying to test algorithms written with api version 2 that is introduced in the new platform release. beat editor shows them as invalid all the time. The experiments are running and the algorithms are correct.https://gitlab.idiap.ch/beat/beat.editor/-/issues/170beat editor is very very very slow2018-12-19T19:02:44ZZohreh MOSTAANIbeat editor is very very very slowI started using beat editor again and I have the latest conda package for it. It is very very slow. So much so that it is almost impossible to work with. I am trying to edit a toolchain, I added one block and then I went to edit the inpu...I started using beat editor again and I have the latest conda package for it. It is very very slow. So much so that it is almost impossible to work with. I am trying to edit a toolchain, I added one block and then I went to edit the inputs of another block, but it goes blank and when I refresh the page it removes all the latest changes. (nothing is saved). I must emphasize that each of these steps that I mentioned are taking a very long time and firefox keeps suggesting to close the page.
I have restarted my firefox and editor server several times but the problem persists.
Please let me know if you need more information.https://gitlab.idiap.ch/beat/docs/-/issues/7Question about documentation.2018-11-09T16:03:22ZZohreh MOSTAANIQuestion about documentation.Could you please tell me which one of these statements are correct. They are both about the same concept in defining arrays in dataformats.
In beat.core/dataformats/arrays: `An array can have as many dimensions as you want.`
In beat.w...Could you please tell me which one of these statements are correct. They are both about the same concept in defining arrays in dataformats.
In beat.core/dataformats/arrays: `An array can have as many dimensions as you want.`
In beat.web/user/dataformat/arrays: `An array can have up to 32 dimensions.`
Thanks.André AnjosAndré Anjoshttps://gitlab.idiap.ch/beat/beat.backend.python/-/issues/19The PyPI trove classifier "Framework :: BEAT" does not work2019-04-11T07:11:40ZAndré AnjosThe PyPI trove classifier "Framework :: BEAT" does not workThe deployment of beat packages in PyPI is broken because they all contain `Framework :: BEAT`. I think we should remove this globally so that the deployment works.
Example: https://gitlab.idiap.ch/beat/beat.backend.python/pipelines/24051The deployment of beat packages in PyPI is broken because they all contain `Framework :: BEAT`. I think we should remove this globally so that the deployment works.
Example: https://gitlab.idiap.ch/beat/beat.backend.python/pipelines/24051Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/52About Walkthrough section in the documentation.2018-12-06T09:50:13ZZohreh MOSTAANIAbout Walkthrough section in the documentation.I do not understand what is the purpose of the section Walkthrough in the documentation of beat.cmdline. Is it for developing the beat platform locally? Is it only for running the platform locally? Or is it for developing the beat.cmdlin...I do not understand what is the purpose of the section Walkthrough in the documentation of beat.cmdline. Is it for developing the beat platform locally? Is it only for running the platform locally? Or is it for developing the beat.cmdline itself? In the first line of this documentation it is written:
This page gives an overview on setting up an environment to develop BEAT **experiments** locally.https://gitlab.idiap.ch/beat/beat.editor/-/issues/169cannot build the virtual image for beat editor.2018-11-20T18:08:52ZZohreh MOSTAANIcannot build the virtual image for beat editor.I cannot make the VM even after using the ``june-allies`` branch.
I installed the packer. The only command I could run is ``packer`` not ``packer-io`` and when I run ``packer build ubuntu-18.04-beat.json`` I get this error:
```
virtualb...I cannot make the VM even after using the ``june-allies`` branch.
I installed the packer. The only command I could run is ``packer`` not ``packer-io`` and when I run ``packer build ubuntu-18.04-beat.json`` I get this error:
```
virtualbox-iso output will be in this color.
==> virtualbox-iso: Downloading or copying Guest additions
virtualbox-iso: Downloading or copying: file:///usr/share/virtualbox/VBoxGuestAdditions.iso
==> virtualbox-iso: Downloading or copying ISO
virtualbox-iso: Downloading or copying: file://./iso/ubuntu-18.04-server-amd64.iso
virtualbox-iso: Error downloading: open /idiap/user/zmostaani/experiments/beat.tutorial/packer_scripts/iso/ubuntu-18.04-server-amd64.iso: no such file or directory
virtualbox-iso: Downloading or copying: http://cdimage.ubuntu.com/ubuntu/releases/bionic/release/ubuntu-18.04-server-amd64.iso
virtualbox-iso: Error downloading: Error making HTTP GET request: 404 Not Found
==> virtualbox-iso: ISO download failed.
Build 'virtualbox-iso' errored: ISO download failed.
```
I followed the steps in the documentation. I am using idiap's workstation which has VirtualBox installed.
It is related to issues #148 and #150.https://gitlab.idiap.ch/beat/beat.web/-/issues/506[doc] missing documentation for account reactivation (blocked users)2018-10-29T08:44:57ZFlavio TARSETTI[doc] missing documentation for account reactivation (blocked users)The FAQ needs an update to target blocked users willing to reactivate their accountThe FAQ needs an update to target blocked users willing to reactivate their accountFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/167[plotterparameter] first plotter selected instead of blank selection and sche...2018-10-31T13:05:04ZFlavio TARSETTI[plotterparameter] first plotter selected instead of blank selection and schema validation is wrong (having 1 plotter selected is a requirement)As in #154 and fixed in my MR !23 we have the same issue for the plotterparameter component:
The selector by default shows the first available plotter as selected, but it should really show a "blank" selection, prompting the user to choo...As in #154 and fixed in my MR !23 we have the same issue for the plotterparameter component:
The selector by default shows the first available plotter as selected, but it should really show a "blank" selection, prompting the user to choose a plotter. It tricks the user to believe that he has selected something BUT in the json file there's no plotter selected.
The plotterparameter believes it is valid even without any plotter. This needs to be fixedFlavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/166[tests] no input validation and empty test files2019-01-21T18:41:25ZFlavio TARSETTI[tests] no input validation and empty test filesA large number of tests for each components are missing and need to be fixed:
- input validation are missing in the `ParameterCreate.jsx`
- some files such as `PlotterParameterEditor.spec.jsx, PlotterEditor.spec.jsx` are empty files (I ...A large number of tests for each components are missing and need to be fixed:
- input validation are missing in the `ParameterCreate.jsx`
- some files such as `PlotterParameterEditor.spec.jsx, PlotterEditor.spec.jsx` are empty files (I am currently working on the `PlotterEditor.spec.jsx`)https://gitlab.idiap.ch/beat/beat.editor/-/issues/165beat editor is down again with new error. may be relavant to issue #149.2019-01-09T18:52:34ZZohreh MOSTAANIbeat editor is down again with new error. may be relavant to issue #149.This time I do not get a blank page when I run the editor but when I check any of the tabs (experiments, algorithms) etc I get a blank page. It happened in the middle of editing some experiment but I do not know where is the problem beca...This time I do not get a blank page when I run the editor but when I check any of the tabs (experiments, algorithms) etc I get a blank page. It happened in the middle of editing some experiment but I do not know where is the problem because the experiment is running.
I get this error on the firefox console:
```
too much recursion[Learn More]
```
and this error on the terminal:
```
[2018-10-15 16:39:26,355] ERROR in app: Exception on /algorithms [GET]
Traceback (most recent call last):
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/flask/app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/flask/app.py", line 1799, in dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/flask_restful/__init__.py", line 480, in wrapper
resp = resource(*args, **kwargs)
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/flask/views.py", line 88, in view
return self.dispatch_request(*args, **kwargs)
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/flask_restful/__init__.py", line 595, in dispatch_request
resp = meth(*args, **kwargs)
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/beat/editor/resources.py", line 339, in get
return self.refresh()
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/beat/editor/resources.py", line 333, in refresh
return generate_entity_tree(entity, self.config)
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/beat/editor/resources.py", line 213, in generate_entity_tree
for f in obj['children']:
KeyError: 'children'
Exception on /algorithms [GET]
Traceback (most recent call last):
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/flask/app.py", line 1813, in full_dispatch_request
rv = self.dispatch_request()
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/flask/app.py", line 1799, in dispatch_request
return self.view_functions[rule.endpoint](**req.view_args)
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/flask_restful/__init__.py", line 480, in wrapper
resp = resource(*args, **kwargs)
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/flask/views.py", line 88, in view
return self.dispatch_request(*args, **kwargs)
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/flask_restful/__init__.py", line 595, in dispatch_request
resp = meth(*args, **kwargs)
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/beat/editor/resources.py", line 339, in get
return self.refresh()
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/beat/editor/resources.py", line 333, in refresh
return generate_entity_tree(entity, self.config)
File "/idiap/user/zmostaani/miniconda3/envs/beat_py3/lib/python3.6/site-packages/beat/editor/resources.py", line 213, in generate_entity_tree
for f in obj['children']:
KeyError: 'children'
```https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/50Pushing experiments to the platform is very tricky without informative warnin...2019-10-23T18:29:10ZZohreh MOSTAANIPushing experiments to the platform is very tricky without informative warnings or errors!The assumption is that you can pull an experiment from the platform, edit the necessary blocks (which means debugging the blocks without going through the pain of making new versions or forks for each block) and then push back to the pla...The assumption is that you can pull an experiment from the platform, edit the necessary blocks (which means debugging the blocks without going through the pain of making new versions or forks for each block) and then push back to the platform.
The issue is that in each experiment the user can use toolchains, or algorithms, etc that are public from other users and when they are pulled they are organized in folders with similar usernames in the user's local prefix folder.
With current setup if users want to edit some algorithm they **should** first copy them to their own name space.
If you do not make new algorithms under your own name space two scenarios may happen:
- You just edited the file from original user (not a good idea). `beat push` command in this situation does not push anything since it already exists on the platform.
- you made new version form the same algorithm which goes under the category of the original user. `beat push` command will create a new algorithm with the same name under your username with version number one without any warnings and it shows on the command line that the algorithm under the original username has been created.
The problem is since there is no error or warnings in such situations and nothing mentioned in the documentation it is tricky to find out where the problem comes from. It might be very confusing for the normal user to interact with beat.https://gitlab.idiap.ch/beat/beat.editor/-/issues/164What does browser-tests stage in the CI do?2019-02-14T22:12:46ZAndré AnjosWhat does browser-tests stage in the CI do?I was making changes to BEAT packages regarding their test-only phases. When running in test-only mode, we should **not** try to build the manual or check the package components anymore, as that will not fly with the current test strate...I was making changes to BEAT packages regarding their test-only phases. When running in test-only mode, we should **not** try to build the manual or check the package components anymore, as that will not fly with the current test strategy.
I made modifications to beat.cmdline and beat.core to take this into account (check latest MRs on those packages), simply making sure that `sphinx` and `conda` based test lines are only executed during the build and not in test-only phases.
I wanted to do the same for this package, but I wonder what the stage `browser-tests` really do. It seems to be not doing more than what is done during `build`.
Could @flavio.tarsetti clarify, please?Flavio TARSETTIFlavio TARSETTIhttps://gitlab.idiap.ch/beat/beat.cmdline/-/issues/49The necessary blocks are not properly checked before pushing an experiment to...2019-10-23T18:29:09ZZohreh MOSTAANIThe necessary blocks are not properly checked before pushing an experiment to the platformI tried to push an experiment to the platform but it was giving the error that certain algorithms do not exist. I had to push each algorithm manually. Also the version number of the algorithm in my local system was 2 but when it was uplo...I tried to push an experiment to the platform but it was giving the error that certain algorithms do not exist. I had to push each algorithm manually. Also the version number of the algorithm in my local system was 2 but when it was uploaded to the platform it changed to one, therefore I got error again and I had to edit my local experiment to use version one so that I be able to upload the whole experiment.https://gitlab.idiap.ch/beat/beat.cmdline/-/issues/48[ci] issue merge request2018-10-15T06:35:52ZFlavio TARSETTI[ci] issue merge requestOn this pipeline:
https://gitlab.idiap.ch/beat/beat.cmdline/pipelines/24234
One of the job output:
https://gitlab.idiap.ch/beat/beat.cmdline/-/jobs/150275
it fails all the time.
any idea why ? @zmostaani @samuel.gaist @andre.anjosOn this pipeline:
https://gitlab.idiap.ch/beat/beat.cmdline/pipelines/24234
One of the job output:
https://gitlab.idiap.ch/beat/beat.cmdline/-/jobs/150275
it fails all the time.
any idea why ? @zmostaani @samuel.gaist @andre.anjoshttps://gitlab.idiap.ch/beat/beat.editor/-/issues/163Disable py27 builds2018-10-09T10:03:52ZAndré AnjosDisable py27 buildsFollowing changes in most packages for BEAT, please disable python 2.7 CI builds.Following changes in most packages for BEAT, please disable python 2.7 CI builds.Flavio TARSETTIFlavio TARSETTI