beat issueshttps://gitlab.idiap.ch/groups/beat/-/issues2019-03-11T13:42:40Zhttps://gitlab.idiap.ch/beat/beat.web/-/issues/517Docs/usage on scheduler/worker need to be updated2019-03-11T13:42:40ZJaden DIEFENBAUGHDocs/usage on scheduler/worker need to be updatedA couple things:
1. The admin docs (`doc/admin/installation.rst`) says to run `./bin/scheduler -vv` and `./bin/worker -vv` to start a single scheduler/worker node. This doesn't work anymore and needs to be updated.
2. Running `./bin/sche...A couple things:
1. The admin docs (`doc/admin/installation.rst`) says to run `./bin/scheduler -vv` and `./bin/worker -vv` to start a single scheduler/worker node. This doesn't work anymore and needs to be updated.
2. Running `./bin/scheduler --help` gives the following message after the usage/options sections:
```
Examples:
To start the scheduling process do the following:
$ scheduler
You can pass the ``-v`` flag to start the scheduler with the logging level
set to ``INFO`` or ``-vv`` to set it to ``DEBUG``. By default, the logging
level is set to ``WARNING`` if no ``-v`` flag is passed.
```
This isn't correct either.
Running `./bin/scheduler` gives the following error:
```
Traceback (most recent call last):
File "./bin/scheduler", line 26, in <module>
sys.exit(beat.web.scripts.scheduler.main())
File "/home/jae/work/beat.web/beat/web/scripts/scheduler.py", line 219, in main
int(arguments['--port']),
TypeError: int() argument must be a string, a bytes-like object or a number, not 'NoneType'
```
I tried providing a valid value to the `--port` argument: `./bin/scheduler --port=9101`, but it gave me a ZMQ error:
```
Traceback (most recent call last):
File "./bin/scheduler", line 26, in <module>
sys.exit(beat.web.scripts.scheduler.main())
File "/home/jae/work/beat.web/beat/web/scripts/scheduler.py", line 222, in main
onWorkerGone = onWorkerGone,
File "/home/jae/miniconda3/envs/beat-web/lib/python3.6/site-packages/beat/core/worker.py", line 99, in __init__
self.socket.bind(self.address)
File "zmq/backend/cython/socket.pyx", line 547, in zmq.backend.cython.socket.Socket.bind
File "zmq/backend/cython/checkrc.pxd", line 25, in zmq.backend.cython.checkrc._check_rc
zmq.error.ZMQError: No such device
```
Trying to start a worker node via `./bin/worker` gives the following message:
```
Usage:
worker [-v ... | --verbose ...] [ --name=<name>] [--prefix=<path>]
[--cache=<path>] [--docker] [--docker-network=<name>]
[--port-range=<range>] <scheduler_address>
worker (--help | -h)
worker (--version | -V)
```
I did all this while `./bin/django runserver` was running in a different window.
This is a blocker on some of my work as I need to run experiments successfully to create reports to work on the report-related issues.Scheduler/Worker resilience improvementSamuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/67Algorithm prototype default dataformat not available on platform installation2019-02-25T08:32:27ZSamuel GAISTAlgorithm prototype default dataformat not available on platform installationThe `integers` dataformat used as default type when loading the algorithm prototype is not available on a default installation of the BEAT platoform.The `integers` dataformat used as default type when loading the algorithm prototype is not available on a default installation of the BEAT platoform.Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/66The plotterparameter type doesn't have a JSON schema file2019-04-18T22:25:57ZJaden DIEFENBAUGHThe plotterparameter type doesn't have a JSON schema fileNot sure what happened but we need one, right?
I found this out by working on https://gitlab.idiap.ch/beat/beat.editor/issues/161Not sure what happened but we need one, right?
I found this out by working on https://gitlab.idiap.ch/beat/beat.editor/issues/161Jaden DIEFENBAUGHJaden DIEFENBAUGHhttps://gitlab.idiap.ch/beat/beat.web/-/issues/516Issues with installing demo data on v1.4.1 and master2019-02-25T18:34:53ZJaden DIEFENBAUGHIssues with installing demo data on v1.4.1 and masterWhen installing the dummy data in a new installation via `./bin/django install`, all the experiments & algorithms aren't installed due to errors (log attached). As I'm working on the reports app, I need at least some data to make reports...When installing the dummy data in a new installation via `./bin/django install`, all the experiments & algorithms aren't installed due to errors (log attached). As I'm working on the reports app, I need at least some data to make reports with.
I tried alot of different things hoping that I was doing something wrong, but I think the test data just hasn't been updated?
Repro:
- Clone beat.web
- Either stay on master or checkout tag `v.1.4.1`
- Run the commands in the README to install beat.web through conda/buildout
- Run `./bin/django install -v1` or `./bin/django install`
Expected:
The example data is installed to the new platform installation successfully and is available when running `./bin/django runserver`.
Actual:
There are only 14 toolchains, 2 libraries, and 10 dataformats available. Nothing else.
Logs:
Log for `./bin/django install`: [install.out](/uploads/8240025bc185d6aeca7d4a6072dafe27/install.out)
Log for `./bin/django install -v1`: [install_v1.out](/uploads/b91feb30aae43465e4a57982e50882d2/install_v1.out)https://gitlab.idiap.ch/beat/beat.editor/-/issues/199Project Bandit settings & assert statements2019-05-09T12:52:53ZJaden DIEFENBAUGHProject Bandit settings & assert statementsShould we not be using assert statements to make runtime checks to make sure things are working properly behind the scenes? From what I understood, that's what we were supposed to use in Python, but the current settings for python-bandit...Should we not be using assert statements to make runtime checks to make sure things are working properly behind the scenes? From what I understood, that's what we were supposed to use in Python, but the current settings for python-bandit flags all assert statements ([B101](https://docs.openstack.org/bandit/latest/plugins/b101_assert_used.html) is active)Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.core/-/issues/65Updates to the algorithm schema2019-02-23T18:21:47ZJaden DIEFENBAUGHUpdates to the algorithm schemaSee the relevant [beat.editor MR](https://gitlab.idiap.ch/beat/beat.editor/merge_requests/46) for how this started.
The algorithm schema is not specific enough, and needs some changing if the JSON schema tech allows it:
- There should b...See the relevant [beat.editor MR](https://gitlab.idiap.ch/beat/beat.editor/merge_requests/46) for how this started.
The algorithm schema is not specific enough, and needs some changing if the JSON schema tech allows it:
- There should be at least 1 output in the algorithm
- Every group should have at least 1 input (otherwise it's an empty group and should be removed)
- Analyzers *maybe* should be required to have at least 1 result
I'm pretty sure they are all possible to encode in the JSON schema.https://gitlab.idiap.ch/beat/beat.editor/-/issues/198smart color picking for the database blocks of a toolchain so that the close ...2020-02-12T12:35:15ZZohreh MOSTAANIsmart color picking for the database blocks of a toolchain so that the close ones are visually distinct.see #152 for info on this.see #152 for info on this.[v2] 2 - Toolchain editorhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/197more information available as comment on the python template produced for dat...2020-02-12T12:34:42ZZohreh MOSTAANImore information available as comment on the python template produced for databases.It would be nice to have the output names and output data types as comment on the python template for a database when you are preparing it using beat editor.It would be nice to have the output names and output data types as comment on the python template for a database when you are preparing it using beat editor.https://gitlab.idiap.ch/beat/beat.editor/-/issues/196rearrange the inputs in a toolchain block2020-06-16T16:03:32ZZohreh MOSTAANIrearrange the inputs in a toolchain blockIt would be very useful if the user is able to reorder the inputs when they are defined in a block. Sometimes you may just make a block with the inputs but it will be easier to connect them to other blocks if they were in another order. ...It would be very useful if the user is able to reorder the inputs when they are defined in a block. Sometimes you may just make a block with the inputs but it will be easier to connect them to other blocks if they were in another order. This is different from renaming though.[v2] 2 - Toolchain editorhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/195visual feedback to the user when the save button is pressed2020-02-12T12:32:25ZZohreh MOSTAANIvisual feedback to the user when the save button is pressedWhen I press the save button after a change in anywhere, there is no graphical feedback to let me know that the save is actually has been done. There were times that in fact the save function has not worked but I could not see it. Right ...When I press the save button after a change in anywhere, there is no graphical feedback to let me know that the save is actually has been done. There were times that in fact the save function has not worked but I could not see it. Right now I refresh the whole page to make sure that the changes are done.[v2] 2 - Toolchain editorhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/194visula distiction between different parameter cathegories on the experiment p...2020-02-12T12:31:57ZZohreh MOSTAANIvisula distiction between different parameter cathegories on the experiment page.It would be nice if the separation between different parameter categories in the experiment page such as Block, Global Settings, etc were more distinct.
This might be resolved in version two with a new design.It would be nice if the separation between different parameter categories in the experiment page such as Block, Global Settings, etc were more distinct.
This might be resolved in version two with a new design.[v2] 3 - Experiment editorhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/193breaking connections in a toolchain to by pass the blocks2020-02-12T12:52:21ZZohreh MOSTAANIbreaking connections in a toolchain to by pass the blocksI think it would be good if the connections in a toolchain could break at some points and bypass blocks instead of directly connecting inputs and outputs. Something like what is available on the beat platform. The reason is that even tho...I think it would be good if the connections in a toolchain could break at some points and bypass blocks instead of directly connecting inputs and outputs. Something like what is available on the beat platform. The reason is that even though it is more convenient while making a toolchain to just connect an output to an input it is very difficult to understand what is going on when you look at an experiment using that toolchain, specially when the experiments get bigger and the connections are crossing each other. Even if there was a mechanism to highlight a chosen connection in the experiment page can be really helpful. This mechanism is already there when making a toolchain but not when you look at the experiment.[v2] 2 - Toolchain editorhttps://gitlab.idiap.ch/beat/docs/-/issues/11Inter-package documentation links are broken2019-06-28T11:36:28ZAndré AnjosInter-package documentation links are brokenInter-package documentation links are not correct at build time because of dependencies or rather depending on packages that are not dependencies (beat.doc is not a dependency of beat.core). The documentation conf.py file should try to g...Inter-package documentation links are not correct at build time because of dependencies or rather depending on packages that are not dependencies (beat.doc is not a dependency of beat.core). The documentation conf.py file should try to grab information from the package like version and the URL for the final documentation from environment variables.Zohreh MOSTAANIZohreh MOSTAANIhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/192[meta] Naming branches to associate it with an issue2019-02-25T11:34:25ZJaden DIEFENBAUGH[meta] Naming branches to associate it with an issueIn `doc/contribute.rst`, we say that "branches should have meaningful names". We give two examples, one of which actually references the issue number. Could we require that all branches directly reference the issue the branch is addressi...In `doc/contribute.rst`, we say that "branches should have meaningful names". We give two examples, one of which actually references the issue number. Could we require that all branches directly reference the issue the branch is addressing? So names like the following are fine:
- "issue_20_fix_wrong_index"
- "implement_db_editor_248"
But names like the following aren't okay except in rare cases:
- "fix_wrong_index"
- "implement_db_editor"
I personally find it hard to understand what someone is doing in a branch when they don't reference an existing issue.
_[edit]_:
Final decision: <issue_number>_name_of_the_branchhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/191Remove v1 artifacts2019-10-04T15:12:54ZJaden DIEFENBAUGHRemove v1 artifactsSummary
There are still some artifacts of the v1 editor in v2:
- `.gitignore` has all the Node/JS stuff still in it
- `beat/editor/js` still exists
- `doc/{index.rst,editor.rst,licenses.rst,img/,svg/}` are all still from v1
What does i...Summary
There are still some artifacts of the v1 editor in v2:
- `.gitignore` has all the Node/JS stuff still in it
- `beat/editor/js` still exists
- `doc/{index.rst,editor.rst,licenses.rst,img/,svg/}` are all still from v1
What does it provide?
Remove all of the above:
- Remove all the JS stuff from `.gitignore`
- Remove the `beat/editor/js` directory
- Remove most of the the text in `doc/index.rst` and just have it point to `doc/contribute.rst` for now
- Remove `doc/{editor.rst,licenses.rst}`
- Save `doc/{img/,svg/}` as we'll probably want to adapt these later for v2 documentationhttps://gitlab.idiap.ch/beat/beat.editor/-/issues/190AssetType Unknown path spelling2019-10-04T15:12:54ZJaden DIEFENBAUGHAssetType Unknown path spellingSummary
The path for an "Unknown" AssetType is misspelled "unkown", which would probably lead to a weird bug months from now if we left it in.
Relevant logs and/or screenshots
https://gitlab.idiap.ch/beat/beat.editor/blob/31bd792c5bd4...Summary
The path for an "Unknown" AssetType is misspelled "unkown", which would probably lead to a weird bug months from now if we left it in.
Relevant logs and/or screenshots
https://gitlab.idiap.ch/beat/beat.editor/blob/31bd792c5bd450167fbf24f39666d86576e43a0b/beat/editor/backend/assetmodel.py#L44Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/189Package "pre-commit" doesn't exist in conda2019-10-04T15:12:54ZJaden DIEFENBAUGHPackage "pre-commit" doesn't exist in condaSummary
@samuel.gaist I've been setting up the v2 branch, following `contribute.rst`. It says to add "pre-commit" through conda. Did you mean "pre_commit"?Summary
@samuel.gaist I've been setting up the v2 branch, following `contribute.rst`. It says to add "pre-commit" through conda. Did you mean "pre_commit"?Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.editor/-/issues/188Add port configuration to v1 for ALLIES partners2019-02-12T18:55:52ZJaden DIEFENBAUGHAdd port configuration to v1 for ALLIES partnersSummary
An ALLIES partner is trying to use beat.editor across an SSH connection and needs better control over the ports used for beat.editor. Right now the editor just uses port 5000 for serving the API/static files (python code) & for ...Summary
An ALLIES partner is trying to use beat.editor across an SSH connection and needs better control over the ports used for beat.editor. Right now the editor just uses port 5000 for serving the API/static files (python code) & for querying the API (JS code).
What does it provide?
Port configuration sufficient for the partner.
Relevant links / references
See https://groups.google.com/d/msg/beat-devel/m9vCN1J6I8E/pA9smNcXEgAJhttps://gitlab.idiap.ch/beat/beat.web/-/issues/515BEAT website certificate and expiration2020-03-30T14:04:20ZAndré AnjosBEAT website certificate and expirationThe BEAT website certificate will expire in March 2020. The domain name will not be renewed, so we need to migrate the location of the official platform (beat.web production deployment).
To avoid a pressing issue then, and leave time f...The BEAT website certificate will expire in March 2020. The domain name will not be renewed, so we need to migrate the location of the official platform (beat.web production deployment).
To avoid a pressing issue then, and leave time for people to "adapt" to a new address, I propose we start looking for solutions now.
@samuel.gaist: Could you please contact the system group (via a ticket) and ask them which solutions could be setup to host the platform under "idiap.ch".
I thought of 2 options, but I'm not sure whether these are feasible:
1. "https://beat.idiap.ch": The advantage is that swagger docs would start working again...
2. "https://www.idiap.ch/software/beat/platform": This would be the one that makes more sense "structurally"Samuel GAISTSamuel GAISThttps://gitlab.idiap.ch/beat/beat.web/-/issues/514Frontpage counters should only display numbers of elements that are publicly ...2020-11-17T14:49:38ZAndré AnjosFrontpage counters should only display numbers of elements that are publicly available (if user not logged in)The current front page counters of the BEAT platform display the total number of objects **available** in the platform - not necessarily available to the current user.
We should change this to display what is the total available to the ...The current front page counters of the BEAT platform display the total number of objects **available** in the platform - not necessarily available to the current user.
We should change this to display what is the total available to the current logged in user and, failing that, to the anonymous user.
It is disappointing for the (anonymous) user to see a smaller number of objects when clicking the links.Samuel GAISTSamuel GAIST