beat.editor issues
https://gitlab.idiap.ch/beat/beat.editor/-/issues
2019-03-07T21:13:26Z
https://gitlab.idiap.ch/beat/beat.editor/-/issues/174
JSON schema duplication
2019-03-07T21:13:26Z
Samuel GAIST
JSON schema duplication
The files found in the conda/js/src/helpers/schema/ subfolder are basically duplicates of the schemas defined in beat.core.
This is wrong on several levels:
- Code duplication
- They are out of sync with the current beat.core version
-...
The files found in the conda/js/src/helpers/schema/ subfolder are basically duplicates of the schemas defined in beat.core.
This is wrong on several levels:
- Code duplication
- They are out of sync with the current beat.core version
- The folder content is not even a copy of the beat.core content so they are currently different
- New versions of the schema are not available
The only official schemas are the ones from beat.core. Those must be used and not copied.
Relates to #140
[v1] Ongoing patching until [v2] is ready
Jaden DIEFENBAUGH
Jaden DIEFENBAUGH
https://gitlab.idiap.ch/beat/beat.editor/-/issues/145
New algorithms should come with an input & output in the first group
2019-02-26T09:51:19Z
Jaden DIEFENBAUGH
New algorithms should come with an input & output in the first group
Pretty sure this is a requirement of non-analyzer algorithms, so it would make sense to do this step for the user
Pretty sure this is a requirement of non-analyzer algorithms, so it would make sense to do this step for the user
[v1] Ongoing patching until [v2] is ready
Jaden DIEFENBAUGH
Jaden DIEFENBAUGH
https://gitlab.idiap.ch/beat/beat.editor/-/issues/164
What does browser-tests stage in the CI do?
2019-02-14T22:12:46Z
André Anjos
What 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 TARSETTI
Flavio TARSETTI
https://gitlab.idiap.ch/beat/beat.editor/-/issues/188
Add port configuration to v1 for ALLIES partners
2019-02-12T18:55:52Z
Jaden DIEFENBAUGH
Add port configuration to v1 for ALLIES partners
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 ...
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/pA9smNcXEgAJ
https://gitlab.idiap.ch/beat/beat.editor/-/issues/176
toolchain naming
2019-02-07T15:06:01Z
Flavio TARSETTI
toolchain naming
During our ALLIES meeting, it has been shown that adding multiple inputs in an object overwrites the names.
For it to work, we need to "add input" then "Save" every time and then re-open the object add another input etc.
What we expect...
During our ALLIES meeting, it has been shown that adding multiple inputs in an object overwrites the names.
For it to work, we need to "add input" then "Save" every time and then re-open the object add another input etc.
What we expect is that adding multiples inputs shouldn't overwrite the previous input names.
@jdiefenbaugh : Can you fix this please? Thanks.
[v1] Ongoing patching until [v2] is ready
Jaden DIEFENBAUGH
Jaden DIEFENBAUGH
https://gitlab.idiap.ch/beat/beat.editor/-/issues/104
Better path to files on the editors
2019-02-07T11:53:56Z
Jaden DIEFENBAUGH
Better path to files on the editors
https://gitlab.idiap.ch/beat/beat.editor/-/issues/166
[tests] no input validation and empty test files
2019-01-21T18:41:25Z
Flavio TARSETTI
[tests] no input validation and empty test files
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 ...
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/162
[algorithm] a "warning" for algorithms
2019-01-18T18:01:51Z
Flavio TARSETTI
[algorithm] a "warning" for algorithms
A strange warning appears when loading algorithms in the interface:
```
Warning: Failed prop type: Invalid prop `children` supplied to `Form`, expected a ReactNode.
in Form (created by AlgorithmEditor)
in AlgorithmEditor (create...
A strange warning appears when loading algorithms in the interface:
```
Warning: Failed prop type: Invalid prop `children` supplied to `Form`, expected a ReactNode.
in Form (created by AlgorithmEditor)
in AlgorithmEditor (created by Connect(AlgorithmEditor))
in Connect(AlgorithmEditor) (created by EntityDetail)
in div (created by TabPane)
in TabPane (created by EntityDetail)
in div (created by TabContent)
in TabContent (created by EntityDetail)
in div (created by Col)
in Col (created by EntityDetail)
in div (created by Row)
in Row (created by EntityDetail)
in div (created by Container)
in Container (created by EntityDetail)
in EntityDetail (created by Connect(EntityDetail))
in Connect(EntityDetail) (created by Route)
in Route (created by EntityHome)
in Switch (created by EntityHome)
in EntityHome (created by MainContent)
in div (created by MainContent)
in MainContent (created by Route)
in Route (created by App)
in Switch (created by App)
in div (created by Container)
in Container (created by App)
in Router (created by HashRouter)
in HashRouter (created by App)
in App (created by HotExportedApp)
in AppContainer (created by HotExportedApp)
in HotExportedApp
in Provider
printWarning @ checkPropTypes.js:19
checkPropTypes @ checkPropTypes.js:82
validatePropTypes @ react.development.js:1300
createElementWithValidation @ react.development.js:1388
React$$1.createElement @ react-hot-loader.development.js:964
AlgorithmEditor.render @ AlgorithmEditor.jsx:566
finishClassComponent @ react-dom.development.js:13193
updateClassComponent @ react-dom.development.js:13155
beginWork @ react-dom.development.js:13824
performUnitOfWork @ react-dom.development.js:15863
workLoop @ react-dom.development.js:15902
renderRoot @ react-dom.development.js:15942
performWorkOnRoot @ react-dom.development.js:16560
performWork @ react-dom.development.js:16482
performSyncWork @ react-dom.development.js:16454
interactiveUpdates$1 @ react-dom.development.js:16719
interactiveUpdates @ react-dom.development.js:2150
dispatchInteractiveEvent @ react-dom.development.js:4532
```
Jaden DIEFENBAUGH
Jaden DIEFENBAUGH
https://gitlab.idiap.ch/beat/beat.editor/-/issues/170
beat editor is very very very slow
2018-12-19T19:02:44Z
Zohreh MOSTAANI
beat editor is very very very slow
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 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/beat.editor/-/issues/150
Specify the `june-allies` branch of `beat.tutorial` in documentation
2018-12-19T19:02:44Z
Jaden DIEFENBAUGH
Specify the `june-allies` branch of `beat.tutorial` in documentation
https://gitlab.idiap.ch/beat/beat.editor/-/issues/144
fix connection line ids prepending '#' to id name
2018-12-19T19:02:44Z
Jaden DIEFENBAUGH
fix connection line ids prepending '#' to id name
Obviously my wires crossed at some point - the `line`s in `ToolchainConnections` have ids that start with '#', making it very hard to select a line by id:
```js
document.querySelector('#\\#training_data-measurements-training_alg-measurem...
Obviously my wires crossed at some point - the `line`s in `ToolchainConnections` have ids that start with '#', making it very hard to select a line by id:
```js
document.querySelector('#\\#training_data-measurements-training_alg-measurements');
```
Woops!
Toolchain Editor: Fixes
https://gitlab.idiap.ch/beat/beat.editor/-/issues/143
The connection in the toolchain is not being updated properly
2018-12-19T19:02:44Z
Zohreh MOSTAANI
The connection in the toolchain is not being updated properly
I made a toolchain from scratch by looking at tutorial/eigenface/1 . I made some mistakes in connecting the endpoints but at the end I corrected them and all the names and connections in my toolchain were the same as this toolchain. Then...
I made a toolchain from scratch by looking at tutorial/eigenface/1 . I made some mistakes in connecting the endpoints but at the end I corrected them and all the names and connections in my toolchain were the same as this toolchain. Then I used my toolchain in an experiment but it was not working. It said that the toolchain is not valid because certain connections are wrong. Looking at the json file of the toolchain, it turned out that the correct connections are added to the list of connections without the previous wrong ones being removed from them and therefore the error. I must say that in the beat editor gui everything seemed correct and valid.
Toolchain Editor: Fixes
Jaden DIEFENBAUGH
Jaden DIEFENBAUGH
https://gitlab.idiap.ch/beat/beat.editor/-/issues/142
cannot unassign an algorithm to a block in the experiment.
2018-12-19T19:02:44Z
Zohreh MOSTAANI
cannot unassign an algorithm to a block in the experiment.
After choosing an algorithm for a block in an experiment it is not possible to assign no algorithm to that block. It is only possible to choose from certain algorithms. This is not the case for the Database though. If there is a problem ...
After choosing an algorithm for a block in an experiment it is not possible to assign no algorithm to that block. It is only possible to choose from certain algorithms. This is not the case for the Database though. If there is a problem in the toolchain and you want to find out where the problem is it would be a good option to unassign an algorithm without deleting the whole block.
Experiment Editor: Fixes
https://gitlab.idiap.ch/beat/beat.editor/-/issues/135
Algorithms made with a group & no group names!
2018-12-19T19:02:44Z
Jaden DIEFENBAUGH
Algorithms made with a group & no group names!
The group names shouldnt be shown/editable by users
The group names shouldnt be shown/editable by users
Miscellaneous Editor-specific Improvements
https://gitlab.idiap.ch/beat/beat.editor/-/issues/134
Implement cache (save/cancel options) for block editor
2018-12-19T19:02:44Z
Jaden DIEFENBAUGH
Implement cache (save/cancel options) for block editor
Toolchain Editor: UX Improvements
https://gitlab.idiap.ch/beat/beat.editor/-/issues/132
graphviz dot: require space between blocks
2018-12-19T19:02:44Z
Jaden DIEFENBAUGH
graphviz dot: require space between blocks
They can be touching - not good
They can be touching - not good
Toolchain Editor: Fixes
https://gitlab.idiap.ch/beat/beat.editor/-/issues/131
Weird edgecases with toolchain validity
2018-12-19T19:02:44Z
Jaden DIEFENBAUGH
Weird edgecases with toolchain validity
Rarely it seems that a toolchain is valid but somehow it's not...
will hopefully probably be fixed by the refactoring & test fixing
Rarely it seems that a toolchain is valid but somehow it's not...
will hopefully probably be fixed by the refactoring & test fixing
Toolchain Editor: Fixes
https://gitlab.idiap.ch/beat/beat.editor/-/issues/130
Don't allow dashes in names
2018-12-19T19:02:44Z
Jaden DIEFENBAUGH
Don't allow dashes in names
It breaks alot of stuff
It breaks alot of stuff
Toolchain Editor: Fixes
https://gitlab.idiap.ch/beat/beat.editor/-/issues/129
Block editor should allow switching inputs
2018-12-19T19:02:44Z
Jaden DIEFENBAUGH
Block editor should allow switching inputs
This is a little tricky - say you have two inputs, `input1` and `input2`. Trying to change the first name to `input2` will fail obviously since there's already an `input2`. But you want to switch them. The only solution now is using a 3r...
This is a little tricky - say you have two inputs, `input1` and `input2`. Trying to change the first name to `input2` will fail obviously since there's already an `input2`. But you want to switch them. The only solution now is using a 3rd name to switch, but this isn't super logical...
not sure how to fix this.
Toolchain Editor: UX Improvements
https://gitlab.idiap.ch/beat/beat.editor/-/issues/128
Dataset blocks should hide/show the same as other blocks
2018-12-19T19:02:44Z
Jaden DIEFENBAUGH
Dataset blocks should hide/show the same as other blocks
Dataset blocks always exist at the bottom of the exp editor - they should only pop up if you click a dataset block. But if you click one dataset block, all of them should pop up
Dataset blocks always exist at the bottom of the exp editor - they should only pop up if you click a dataset block. But if you click one dataset block, all of them should pop up
Experiment Editor: Fixes