VISPA web issueshttps://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues2019-05-20T17:08:59+02:00https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/263user don't get any feedback that login failed2019-05-20T17:08:59+02:00Benjamin Fischeruser don't get any feedback that login failedPOST http://localhost:4283/ajax/login
gives
{“msg”: “Unknown user”, “success”: false}
user don’t get any feedback that login failed
*(from redmine: issue id 1298, created on 2013-04-15 by root, closed on 2013-12-18)*POST http://localhost:4283/ajax/login
gives
{“msg”: “Unknown user”, “success”: false}
user don’t get any feedback that login failed
*(from redmine: issue id 1298, created on 2013-04-15 by root, closed on 2013-12-18)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/262workspace host can't consist of umlaute2019-05-20T17:09:00+02:00Benjamin Fischerworkspace host can't consist of umlauteyou are not allowed to use umlaute in the “host” field of the workspace
configuration. Because umlaute are allowed in user specific connections
in the .ssh/config they should also be allowed in vispa.
*(from redmine: issue id 1296, cre...you are not allowed to use umlaute in the “host” field of the workspace
configuration. Because umlaute are allowed in user specific connections
in the .ssh/config they should also be allowed in vispa.
*(from redmine: issue id 1296, created on 2013-04-04 by Christian.Glaser, closed on 2014-03-30)*
* Relations:
* parent #16041.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/261workspace configuration2019-05-20T17:09:00+02:00Benjamin Fischerworkspace configurationif a new workspace is created using the “add workspace” menu entry the
new workspace is not visible in the list of workspaces. A logout is
required to see the workspace
*(from redmine: issue id 1295, created on 2013-04-04 by Christian....if a new workspace is created using the “add workspace” menu entry the
new workspace is not visible in the list of workspaces. A logout is
required to see the workspace
*(from redmine: issue id 1295, created on 2013-04-04 by Christian.Glaser, closed on 2013-12-18)*https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/260Fileselector is missing some style sheets2019-05-20T16:25:25+02:00Benjamin FischerFileselector is missing some style sheetsGET
http://localhost:4282/vispa/static/js/base/file/fileselector/fileselector.js?0
404 (Not Found)
*(from redmine: issue id 1294, created on 2013-03-20 by root, closed on 2013-03-20)*GET
http://localhost:4282/vispa/static/js/base/file/fileselector/fileselector.js?0
404 (Not Found)
*(from redmine: issue id 1294, created on 2013-03-20 by root, closed on 2013-03-20)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/259bin/vispa goes daemon2019-05-20T16:25:24+02:00Benjamin Fischerbin/vispa goes daemonUnder unknown circumstances, the bin/vispa program goes after some time
daemonic when previously started from console (maybe likely during an
exception or misbehaving code).
*(from redmine: issue id 1293, created on 2013-03-18 by root,...Under unknown circumstances, the bin/vispa program goes after some time
daemonic when previously started from console (maybe likely during an
exception or misbehaving code).
*(from redmine: issue id 1293, created on 2013-03-18 by root, closed on 2015-01-12)*1.1https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/258Logging not working as expected2019-05-20T16:25:23+02:00Benjamin FischerLogging not working as expectedWhen starting vispa with `./bin/vispa -l info`, the console output is
`[15/Mar/2013:11:35:25] ENGINE Creating database`
`INFO:cherrypy.error:[15/Mar/2013:11:35:25] ENGINE Creating database`
`[15/Mar/2013:11:35:25] ENGINE Started mo...When starting vispa with `./bin/vispa -l info`, the console output is
`[15/Mar/2013:11:35:25] ENGINE Creating database`
`INFO:cherrypy.error:[15/Mar/2013:11:35:25] ENGINE Creating database`
`[15/Mar/2013:11:35:25] ENGINE Started monitor thread '_TimeoutMonitor'.`
`INFO:cherrypy.error:[15/Mar/2013:11:35:25] ENGINE Started monitor thread '_TimeoutMonitor'.`
`[15/Mar/2013:11:35:25] ENGINE Serving on 127.0.0.1:4282`
`INFO:cherrypy.error:[15/Mar/2013:11:35:25] ENGINE Serving on 127.0.0.1:4282`
`[15/Mar/2013:11:35:25] ENGINE Bus STARTED`
`INFO:cherrypy.error:[15/Mar/2013:11:35:25] ENGINE Bus STARTED`
The occurance of double logs seems to be buggy.
*(from redmine: issue id 1292, created on 2013-03-15 by root, closed on 2013-03-15)*
* Changesets:
* Revision 346 on 2013-03-15T11:49:52Z:
```
fix #1292: double logging to console
```
* Revision 346 on 2013-03-15T11:49:52Z:
```
fix #1292: double logging to console
```1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/257cleanup_workspace in rpc.py throws exception2019-05-20T16:25:22+02:00Benjamin Fischercleanup_workspace in rpc.py throws exceptionWhen shutting down an rpc connection (on `SIGINT`), an type error is
thrown:
`Exception TypeError: "'NoneType' object is not callable" in <bound method Client.__del__ of <vispa.rpc.Client object at 0x10fc4f5d0>> ignored`
This is caused...When shutting down an rpc connection (on `SIGINT`), an type error is
thrown:
`Exception TypeError: "'NoneType' object is not callable" in <bound method Client.__del__ of <vispa.rpc.Client object at 0x10fc4f5d0>> ignored`
This is caused by
`client = pushy.client.PushyClient(self.__target, python=self.__python)`
in vispa/rpc.py, line 123 (in Rev. 336).
In addition, `del client` could be used instead of `client.close()` in
ClientPool.*del*, line 188.
*(from redmine: issue id 1291, created on 2013-03-14 by root, closed on 2014-09-09)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/256Offline extension introduces new dependence on lxml package2019-05-20T16:25:22+02:00Benjamin FischerOffline extension introduces new dependence on lxml packagelxml should only be imported on worker
*(from redmine: issue id 1290, created on 2013-03-01 by root, closed on 2014-04-24)*lxml should only be imported on worker
*(from redmine: issue id 1290, created on 2013-03-01 by root, closed on 2014-04-24)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/255Dirpath cannot be closed2019-05-20T17:09:00+02:00Benjamin FischerDirpath cannot be closedIf Dirpath is opened (tab), it cannot be closed anymore unless one
selects a path OR clicks anywhere on the pathbar …
Feature: One would also intuitively expect that the autocompletion opens
(without pressing the TAB key) if one clicks ...If Dirpath is opened (tab), it cannot be closed anymore unless one
selects a path OR clicks anywhere on the pathbar …
Feature: One would also intuitively expect that the autocompletion opens
(without pressing the TAB key) if one clicks on the textfield “~/” …
*(from redmine: issue id 1289, created on 2013-02-28 by root, closed on 2013-03-14)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/254Three framework missing2019-05-20T17:09:00+02:00Benjamin FischerThree framework missingConsole throws error
*(from redmine: issue id 1288, created on 2013-02-28 by root, closed on 2013-03-01)*Console throws error
*(from redmine: issue id 1288, created on 2013-02-28 by root, closed on 2013-03-01)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/253Logging2019-05-20T17:09:00+02:00Benjamin FischerLoggingLogging mechanism and its setup is not correct
*(from redmine: issue id 1286, created on 2013-02-21 by root, closed on 2013-12-18)*Logging mechanism and its setup is not correct
*(from redmine: issue id 1286, created on 2013-02-21 by root, closed on 2013-12-18)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/252error: notify is not defined2019-05-20T17:09:02+02:00Benjamin Fischererror: notify is not definednotify is not defined
return notify(newData);
messenger.js (line 354)
occurred while polling and changing the size of the main panel …
*(from redmine: issue id 1285, created on 2013-02-20 by root, closed on 2013-03-14)*notify is not defined
return notify(newData);
messenger.js (line 354)
occurred while polling and changing the size of the main panel …
*(from redmine: issue id 1285, created on 2013-02-20 by root, closed on 2013-03-14)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/251faulty WebSocket connected message appears2019-05-20T17:09:03+02:00Benjamin Fischerfaulty WebSocket connected message appearsIn the firebug console, the following message appears even if Firefox 10
is used (and polling starts, i.e. web sockets should be disabled)
“WebSocket connected bus.js…0247.06 (line 6)”
*(from redmine: issue id 1284, created on 2013-02...In the firebug console, the following message appears even if Firefox 10
is used (and polling starts, i.e. web sockets should be disabled)
“WebSocket connected bus.js…0247.06 (line 6)”
*(from redmine: issue id 1284, created on 2013-02-20 by root, closed on 2013-02-20)*
* Changesets:
* Revision 154 by Marcel Rieger on 2013-02-20T15:08:23Z:
```
Fix #1284.
```
* Revision 154 by Marcel Rieger on 2013-02-20T15:08:23Z:
```
Fix #1284.
```1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/249Codeeditor doesn't read xml file2019-05-20T17:09:03+02:00Benjamin FischerCodeeditor doesn't read xml fileCurrently, it is not possible to read xml-like files (identified by MIME
type) with the codeeditor.
*(from redmine: issue id 1282, created on 2013-02-07 by root, closed on 2013-03-14)*Currently, it is not possible to read xml-like files (identified by MIME
type) with the codeeditor.
*(from redmine: issue id 1282, created on 2013-02-07 by root, closed on 2013-03-14)*1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/247The server (serve.py) should be callable from outside the project folder2019-05-20T16:25:16+02:00Benjamin FischerThe server (serve.py) should be callable from outside the project folderWhen typing (e.g.) “python <supfolder>/serve.py” the server doesn’t
start.
*(from redmine: issue id 1273, created on 2013-01-19 by root, closed on 2013-01-19)*
* Changesets:
* Revision 85 by Marcel Rieger on 2013-01-19T17:34:33Z:
`...When typing (e.g.) “python <supfolder>/serve.py” the server doesn’t
start.
*(from redmine: issue id 1273, created on 2013-01-19 by root, closed on 2013-01-19)*
* Changesets:
* Revision 85 by Marcel Rieger on 2013-01-19T17:34:33Z:
```
Fix #1273 (project basedir).
```
* Revision 85 by Marcel Rieger on 2013-01-19T17:34:33Z:
```
Fix #1273 (project basedir).
```1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/246Sometimes log messages are repeated / overlapped with cherrypy's logs.2019-05-20T17:09:03+02:00Benjamin FischerSometimes log messages are repeated / overlapped with cherrypy's logs.1. When setting all loggers to “consoleLogger” a lot of log messages are
repeated, e.g.:
…
2013-01-19 15:01:57,624 - system.cherrypy.ENGINE - INFO - Started
monitor thread ‘Autoreloader’.
2013-01-19 15:01:57,624 - system.cherrypy.E...1. When setting all loggers to “consoleLogger” a lot of log messages are
repeated, e.g.:
…
2013-01-19 15:01:57,624 - system.cherrypy.ENGINE - INFO - Started
monitor thread ‘Autoreloader’.
2013-01-19 15:01:57,624 - system.cherrypy.ENGINE - INFO - Started
monitor thread ‘Autoreloader’.
2013-01-19 15:01:57,732 - system.cherrypy.ENGINE - INFO - Serving on
0.0.0.0:4282
2013-01-19 15:01:57,732 - system.cherrypy.ENGINE - INFO - Serving on
0.0.0.0:4282
2013-01-19 15:01:57,733 - system.cherrypy.ENGINE - INFO - Bus STARTED
2013-01-19 15:01:57,733 - system.cherrypy.ENGINE - INFO - Bus STARTED
2. The cherrypy logger should be disabled in order to avoid interfering
logs like:
127.0.0.1 - - \[19/Jan/2013:15:04:46\] “GET
/vispa/static/img/menuicon\_disabled.png HTTP/1.1” 200 2915
“http://localhost:4282/vispa/” “Mozilla/5.0 (Macintosh; Intel Mac OS X
10\_8\_2) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.52
Safari/537.17”
2013-01-19 15:04:46,033 - access.cherrypy - INFO - 127.0.0.1 - -
\[19/Jan/2013:15:04:46\] “GET /vispa/static/img/menuicon\_disabled.png
HTTP/1.1” 200 2915 “http://localhost:4282/vispa/” “Mozilla/5.0
(Macintosh; Intel Mac OS X 10\_8\_2) AppleWebKit/537.17 (KHTML, like
Gecko) Chrome/24.0.1312.52 Safari/537.17”
*(from redmine: issue id 1272, created on 2013-01-19 by root, closed on 2013-01-28)*0.5https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/245Console logging should be activated by default (in the sample file)2019-05-20T17:09:03+02:00Benjamin FischerConsole logging should be activated by default (in the sample file)When checking out a clean copy from the repo,
the console logging is deactivated by default.
Additionally, comments/explanations would be helpful
(e.g. difference system &lt;->root logger).
Maybe a few lines of instructions in th...When checking out a clean copy from the repo,
the console logging is deactivated by default.
Additionally, comments/explanations would be helpful
(e.g. difference system <->root logger).
Maybe a few lines of instructions in the sample file
are necessary.
*(from redmine: issue id 1271, created on 2013-01-19 by root, closed on 2013-01-28)*0.5https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/244can't open module options when path points to non accasible file2019-05-20T17:09:04+02:00Benjamin Fischercan't open module options when path points to non accasible fileif the field “filename” points to a file where the user has no access
to, the module options don’t show up ->the user has no possibility
to change/solve the problem.
*(from redmine: issue id 1270, created on 2013-01-17 by Christian.Gla...if the field “filename” points to a file where the user has no access
to, the module options don’t show up ->the user has no possibility
to change/solve the problem.
*(from redmine: issue id 1270, created on 2013-01-17 by Christian.Glaser, closed on 2013-01-19)*0.5https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/242Check all configuration files and their options2019-05-20T16:25:12+02:00Benjamin FischerCheck all configuration files and their optionsBefore release:
- Comment, sort and check (if they even needed) all options in the
configurations files.
- Handle the case of misconfiguration, e.g. print error message to
console.
*(from redmine: issue id 1268, created on...Before release:
- Comment, sort and check (if they even needed) all options in the
configurations files.
- Handle the case of misconfiguration, e.g. print error message to
console.
*(from redmine: issue id 1268, created on 2013-01-10 by root, closed on 2013-02-06)*0.5https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/241Open PXLIO File throws error if folder does not exist2019-05-20T17:09:04+02:00Benjamin FischerOpen PXLIO File throws error if folder does not existi) Checkout VISPA@Web
ii) use “Open PXLIO File” from the main menu
The following error is thrown (see webconsole):
“NetworkError: 500 Internal Server Error -
http://localhost:4282/ajax/vfs/filelist”
… Error: \[Exception… “Componen...i) Checkout VISPA@Web
ii) use “Open PXLIO File” from the main menu
The following error is thrown (see webconsole):
“NetworkError: 500 Internal Server Error -
http://localhost:4282/ajax/vfs/filelist”
… Error: \[Exception… “Component returned failure code: 0x80004005
(NS\_ERROR\_FAILURE)” nsresult: “0x80004005 (NS\_ERROR\_FAILURE)”
location: “JS frame ::
http://localhost:4282/static/js/dojo/dojo.js?1357213262.85 ::
<TOP_LEVEL> :: line 15” data: no\] …
\- The error appears because the folder “var/examples/data” does not
exist (?) with vanilla vispa@web. This error should be handled by the
filebrowser (?) and the error msg should be forwarded to the user. Until
now, it is hiddenin the webconsole.
- The examples/data folder should be created automatically by vispa if
the “Open PXLIO File” button has a hard-coded link to that folder.
*(from redmine: issue id 1267, created on 2013-01-08 by root, closed on 2013-01-14)*
* Changesets:
* Revision 1172 by Marcel Rieger on 2013-01-14T13:01:18Z:
```
Fix #1267. Open file selector in user/ when opening a pxlio browser.
```
* Revision 1172 by Marcel Rieger on 2013-01-14T13:01:18Z:
```
Fix #1267. Open file selector in user/ when opening a pxlio browser.
```0.5