VISPA web issueshttps://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues2019-05-20T16:25:27+02:00https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/264support for condor in jobdashboard2019-05-20T16:25:27+02:00Benjamin Fischersupport for condor in jobdashboardcurrently, only jobs from ‘local’ are supported.
*(from redmine: issue id 1299, created on 2013-04-15 by root, closed on 2014-09-05)*currently, only jobs from ‘local’ are supported.
*(from redmine: issue id 1299, created on 2013-04-15 by root, closed on 2014-09-05)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/269Add possibility to load environment variables in rpc mechanism2019-05-20T16:25:30+02:00Benjamin FischerAdd possibility to load environment variables in rpc mechanismVISPA should allow the user to setup their workspace at startup with
“.bashrc”, “.profile”, or user-defined (python) scripts
*(from redmine: issue id 1308, created on 2013-05-06 by root, closed on 2014-04-24)*VISPA should allow the user to setup their workspace at startup with
“.bashrc”, “.profile”, or user-defined (python) scripts
*(from redmine: issue id 1308, created on 2013-05-06 by root, closed on 2014-04-24)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/273File selector does not display folder with unresolved symbolic links2019-05-20T16:25:33+02:00Benjamin FischerFile selector does not display folder with unresolved symbolic linksIf a symbolic link which can not be resolved (e.g. a second HDD is not
mounted) is in a folder, this folder can not be displayed correctly.
Only the first file/subfolder is displayed.
*(from redmine: issue id 1315, created on 2013-05-3...If a symbolic link which can not be resolved (e.g. a second HDD is not
mounted) is in a folder, this folder can not be displayed correctly.
Only the first file/subfolder is displayed.
*(from redmine: issue id 1315, created on 2013-05-30 by Christian.Glaser, closed on 2013-12-18)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/274Parameter Range in Job Designer2019-05-20T16:25:33+02:00Benjamin FischerParameter Range in Job DesignerIt is not possible to create a parameter range.
When a python script is used to define a parameter range (e.g. return
range(3)) the preview value is “ERROR”. However the response from the
ajax request is “{”data“: {”scriptStatus“: true...It is not possible to create a parameter range.
When a python script is used to define a parameter range (e.g. return
range(3)) the preview value is “ERROR”. However the response from the
ajax request is “{”data“: {”scriptStatus“: true, ”valueslist“: ”\[0, 1,
2\]“, ”success“: true}, ”success“: true}”
When the parameter range is created one gets the error message:
“Couldn’t add the parameter range!
Reason: ‘parameterRangeList’”
*(from redmine: issue id 1321, created on 2013-07-10 by Christian.Glaser, closed on 2014-09-05)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/275Job Designer option decorator2019-05-20T16:25:34+02:00Benjamin FischerJob Designer option decoratorIt is not possible to create an option decorator. One gets the error
message:
“Couldn’t add the option decorator!
Reason: ‘optionDecoratorList’”
*(from redmine: issue id 1323, created on 2013-07-10 by Christian.Glaser, closed on 20...It is not possible to create an option decorator. One gets the error
message:
“Couldn’t add the option decorator!
Reason: ‘optionDecoratorList’”
*(from redmine: issue id 1323, created on 2013-07-10 by Christian.Glaser, closed on 2014-09-05)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/276FileSelector does not return expaned path2019-05-20T16:25:35+02:00Benjamin FischerFileSelector does not return expaned pathfile selector returns “~/path/file.txt” and not
“/home/user/path/file.txt” which leads to errors in following modules
*(from redmine: issue id 1379, created on 2013-08-22 by Christian.Glaser, closed on 2014-04-04)*file selector returns “~/path/file.txt” and not
“/home/user/path/file.txt” which leads to errors in following modules
*(from redmine: issue id 1379, created on 2013-08-22 by Christian.Glaser, closed on 2014-04-04)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/277file renaming not working2019-05-20T16:25:35+02:00Benjamin Fischerfile renaming not workingAfter entering a new name of a file (the ‘Enter a new name’ window
shows), the old name is not updated.
*(from redmine: issue id 1442, created on 2013-10-12 by root, closed on 2014-04-04)*After entering a new name of a file (the ‘Enter a new name’ window
shows), the old name is not updated.
*(from redmine: issue id 1442, created on 2013-10-12 by root, closed on 2014-04-04)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/279Fix logging file paths.2019-05-20T16:25:36+02:00Benjamin FischerFix logging file paths.The logging file paths in conf/logging.ini(.sample) are always relative
to the project base path.
However, the server uses ~/.vispa-1.0 as target path for var data, such
as logs, database, etc.
This results in errors like:
IOError: ...The logging file paths in conf/logging.ini(.sample) are always relative
to the project base path.
However, the server uses ~/.vispa-1.0 as target path for var data, such
as logs, database, etc.
This results in errors like:
IOError: \[Errno 2\] No such file or directory:
‘~/vispa/web/vispa1.0/var/logs/vispa.log’
Suggestion:
The (logging) config files should access the serve config.
*(from redmine: issue id 1466, created on 2013-11-11 by root, closed on 2014-04-24)*
* Changesets:
* Revision 1292 on 2014-04-24T12:06:14Z:
```
fix logging path, fixes #1466
```
* Revision 1292 on 2014-04-24T12:06:14Z:
```
fix logging path, fixes #1466
```1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/282Workspace validation method2019-05-20T16:25:38+02:00Benjamin FischerWorkspace validation methodWhen adding or configuring a workspace it is helpful to check the
connection (even before the workspace is added to the db).
There is a prepared method “is\_valid” in
vispa.models.workspace.Workspace:49 (as of rev. 852) which is not
imp...When adding or configuring a workspace it is helpful to check the
connection (even before the workspace is added to the db).
There is a prepared method “is\_valid” in
vispa.models.workspace.Workspace:49 (as of rev. 852) which is not
implemented yet
but already in use.
*(from redmine: issue id 1501, created on 2013-12-30 by root)*2.1https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/283Hostnames from the local ssh config cannot be used as workspace hosts2019-05-20T16:25:39+02:00Benjamin FischerHostnames from the local ssh config cannot be used as workspace hostsI get the following error:
2013-12-31 12:38:17,430 - paramiko.hostkeys - INFO - Not enough fields found in known_hosts in line 109 ('ssh-rsa <my_ssh_key>')
Traceback (most recent call last):
File "/Users/marcel/3PIA/vispa/...I get the following error:
2013-12-31 12:38:17,430 - paramiko.hostkeys - INFO - Not enough fields found in known_hosts in line 109 ('ssh-rsa <my_ssh_key>')
Traceback (most recent call last):
File "/Users/marcel/3PIA/vispa/web/vispa1.0/vispa/tools/ajax.py", line 19, in wrap
content = innerfunc(*args, **kwargs)
File "/Library/Python/2.7/site-packages/cherrypy/_cpdispatch.py", line 34, in __call__
return self.callable(*self.args, **self.kwargs)
File "/Users/marcel/3PIA/vispa/web/vispa1.0/vispa/controller/ajax.py", line 184, in connectworkspace
vispa.workspace.connect(workspace, user, db, password)
File "/Users/marcel/3PIA/vispa/web/vispa1.0/vispa/workspace.py", line 651, in connect
return _connection_pool.get(user, workspace, password=password)
File "/Users/marcel/3PIA/vispa/web/vispa1.0/vispa/workspace.py", line 501, in get
client = self._try_host(user, workspace, host, **kwargs)
File "/Users/marcel/3PIA/vispa/web/vispa1.0/vispa/workspace.py", line 464, in _try_host
client.open()
File "/Users/marcel/3PIA/vispa/web/vispa1.0/vispa/workspace.py", line 379, in open
key=self.__key)
File "/Users/marcel/3PIA/vispa/web/vispa1.0/vispa/workspace.py", line 265, in __init__
self.__client.connect(**connect_args)
File "/Library/Python/2.7/site-packages/paramiko/client.py", line 291, in connect
for (family, socktype, proto, canonname, sockaddr) in socket.getaddrinfo(hostname, port, socket.AF_UNSPEC, socket.SOCK_STREAM):
*(from redmine: issue id 1502, created on 2013-12-31 by root)*2.1https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/286Websockets2019-05-20T16:25:41+02:00Benjamin FischerWebsocketsIf websockets are activated we need as additional dependency: ws4py
*(from redmine: issue id 1527, created on 2014-01-27 by martin.urban, closed on 2014-01-27)*
* Changesets:
* Revision 995 by Marcel Rieger on 2014-01-27T09:34:41Z:
...If websockets are activated we need as additional dependency: ws4py
*(from redmine: issue id 1527, created on 2014-01-27 by martin.urban, closed on 2014-01-27)*
* Changesets:
* Revision 995 by Marcel Rieger on 2014-01-27T09:34:41Z:
```
Add ws4py to dependencies, fix #1527.
```
* Revision 995 by Marcel Rieger on 2014-01-27T09:34:41Z:
```
Add ws4py to dependencies, fix #1527.
```1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/287Upload of binary files2019-05-20T16:25:41+02:00Benjamin FischerUpload of binary filesUpload of binary files is not working due to the RPC mechanism. Data
arrive on server but not on remote side.
*(from redmine: issue id 1528, created on 2014-01-27 by martin.urban, closed on 2014-09-10)*Upload of binary files is not working due to the RPC mechanism. Data
arrive on server but not on remote side.
*(from redmine: issue id 1528, created on 2014-01-27 by martin.urban, closed on 2014-09-10)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/290File extension: loading status could be shown with a delay/timeout.2019-05-20T16:25:43+02:00Benjamin FischerFile extension: loading status could be shown with a delay/timeout.setTimeout + clearTimeout.
*(from redmine: issue id 1531, created on 2014-01-27 by root, closed on 2014-10-02)*
* Changesets:
* Revision 1558 by Marcel Rieger on 2014-10-02T12:20:17Z:
```
Fix loader state when there are many items,...setTimeout + clearTimeout.
*(from redmine: issue id 1531, created on 2014-01-27 by root, closed on 2014-10-02)*
* Changesets:
* Revision 1558 by Marcel Rieger on 2014-10-02T12:20:17Z:
```
Fix loader state when there are many items, fix #1531.
```
* Revision 1558 by Marcel Rieger on 2014-10-02T12:20:17Z:
```
Fix loader state when there are many items, fix #1531.
```1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/297scrolling in filebrowser2019-05-20T16:25:48+02:00Benjamin Fischerscrolling in filebrowserscrolling bug while scrolling back to the top of the table
*(from redmine: issue id 1538, created on 2014-01-29 by Daniel.Van.Asseldonk, closed on 2014-07-21)*
* Changesets:
* Revision 1360 by Martin Urban on 2014-07-21T16:30:57Z:
...scrolling bug while scrolling back to the top of the table
*(from redmine: issue id 1538, created on 2014-01-29 by Daniel.Van.Asseldonk, closed on 2014-07-21)*
* Changesets:
* Revision 1360 by Martin Urban on 2014-07-21T16:30:57Z:
```
File: Improve scrolling, fix #1538
```
* Revision 1360 by Martin Urban on 2014-07-21T16:30:57Z:
```
File: Improve scrolling, fix #1538
```1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/300File extension: use dynamic layout information in "getContextMenuPosition"2019-05-20T16:25:49+02:00Benjamin FischerFile extension: use dynamic layout information in "getContextMenuPosition"*(from redmine: issue id 1545, created on 2014-02-10 by root, closed on 2014-04-08)**(from redmine: issue id 1545, created on 2014-02-10 by root, closed on 2014-04-08)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/301open files with file selector2019-05-20T16:25:50+02:00Benjamin Fischeropen files with file selectorfile are opend just by clicking on the file in the file selector.
they have to be opend after clicking on the “select” button
*(from redmine: issue id 1589, created on 2014-03-18 by Daniel.Van.Asseldonk, closed on 2014-04-04)*file are opend just by clicking on the file in the file selector.
they have to be opend after clicking on the “select” button
*(from redmine: issue id 1589, created on 2014-03-18 by Daniel.Van.Asseldonk, closed on 2014-04-04)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/302connect to workspaces2019-05-20T16:25:51+02:00Benjamin Fischerconnect to workspacescan successfully connect to portal.physik@rwth-aachen.de but not to
lxplus@cern.ch
*(from redmine: issue id 1592, created on 2014-03-18 by Daniel.Van.Asseldonk, closed on 2014-04-24)*can successfully connect to portal.physik@rwth-aachen.de but not to
lxplus@cern.ch
*(from redmine: issue id 1592, created on 2014-03-18 by Daniel.Van.Asseldonk, closed on 2014-04-24)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/304contex menu in filebrowser2019-05-20T16:25:52+02:00Benjamin Fischercontex menu in filebrowserdoing a right click in a filebrowser also opens a context menu in other
filbowsers/workspaces.
furthermore, right contextmenus only work in the first opend
filebrowser.
*(from redmine: issue id 1596, created on 2014-03-19 by Daniel.Va...doing a right click in a filebrowser also opens a context menu in other
filbowsers/workspaces.
furthermore, right contextmenus only work in the first opend
filebrowser.
*(from redmine: issue id 1596, created on 2014-03-19 by Daniel.Van.Asseldonk, closed on 2014-03-28)*1.02014-03-28https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/312Hook "user.logout" freezes the server2019-05-20T16:25:59+02:00Benjamin FischerHook "user.logout" freezes the serverWhen a user logs out and there are proxy objects in the pool,
the server freezes.
The logout action is performed in the /logout controller in the line
vispa.fire_callback("user.logout", cherrypy.request.user)
The last logs are
...When a user logs out and there are proxy objects in the pool,
the server freezes.
The logout action is performed in the /logout controller in the line
vispa.fire_callback("user.logout", cherrypy.request.user)
The last logs are
2014-03-27 18:15:36,780 - vispa.workspace - INFO - clear client 1 1
2014-03-27 18:15:36,780 - vispa.workspace - DEBUG - close rpyc
2014-03-27 18:15:36,780 - vispa.workspace - DEBUG - close transport
*(from redmine: issue id 1611, created on 2014-03-27 by root, closed on 2014-09-05)*
* Relations:
* child #16161.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/314system crashes after disconnecting a workspace2019-05-20T16:26:00+02:00Benjamin Fischersystem crashes after disconnecting a workspacevispa crashes, when trying to disconnect from a workspace while a
filebrowser is opened.
the terminal, from which the vispa server had been started, has to be
closed. just restarting the server in the same terminal does not work.
*(f...vispa crashes, when trying to disconnect from a workspace while a
filebrowser is opened.
the terminal, from which the vispa server had been started, has to be
closed. just restarting the server in the same terminal does not work.
*(from redmine: issue id 1616, created on 2014-03-28 by Daniel.Van.Asseldonk, closed on 2014-04-24)*
* Relations:
* parent #16111.0