VISPA web issueshttps://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues2019-05-20T16:23:39+02:00https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/106secure filesystem2019-05-20T16:23:39+02:00Benjamin Fischersecure filesystemfile and folder access is not checked.
*(from redmine: issue id 708, created on 2011-09-18 by gmueller, closed on 2013-01-07)*file and folder access is not checked.
*(from redmine: issue id 708, created on 2011-09-18 by gmueller, closed on 2013-01-07)*0.2https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/278Job Status Dashboard2019-05-20T17:08:58+02:00Benjamin FischerJob Status DashboardBei jedem ersten erstmaligen Ausführen nach einloggen eines Jobs,
bekommt der Job den Status “Unknown”. Der Refresh Button ändert daran
nichts. Ein output wird aber erzeugt.
*(from redmine: issue id 1463, created on 2013-11-06 by Danie...Bei jedem ersten erstmaligen Ausführen nach einloggen eines Jobs,
bekommt der Job den Status “Unknown”. Der Refresh Button ändert daran
nichts. Ein output wird aber erzeugt.
*(from redmine: issue id 1463, created on 2013-11-06 by Daniel.Van.Asseldonk, closed on 2014-03-19)*0.3https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/198Opem existing filebroser tab for same folder2019-05-20T16:24:40+02:00Benjamin FischerOpem existing filebroser tab for same folder*(from redmine: issue id 1086, created on 2012-07-23 by gmueller, closed on 2013-01-07)**(from redmine: issue id 1086, created on 2012-07-23 by gmueller, closed on 2013-01-07)*0.3https://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 <->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.5https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/236Lightbox in browser view not working for pdfs2019-05-20T17:09:05+02:00Benjamin FischerLightbox in browser view not working for pdfsWith current tip (rev. 1150), one is not able to view pdf inside the
browser (tested on firefox)
*(from redmine: issue id 1256, created on 2012-11-28 by root, closed on 2013-01-14)*
* Changesets:
* Revision 1174 by Marcel Rieger on ...With current tip (rev. 1150), one is not able to view pdf inside the
browser (tested on firefox)
*(from redmine: issue id 1256, created on 2012-11-28 by root, closed on 2013-01-14)*
* Changesets:
* Revision 1174 by Marcel Rieger on 2013-01-14T14:52:30Z:
```
Fix #1256. Pdf files must be downloaded now (image file can still be displayed with the lightbox plugin).
```
* Revision 1174 by Marcel Rieger on 2013-01-14T14:52:30Z:
```
Fix #1256. Pdf files must be downloaded now (image file can still be displayed with the lightbox plugin).
```0.5https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/231Analysis Dashboard issues "Connection refused" error2019-05-20T17:09:05+02:00Benjamin FischerAnalysis Dashboard issues "Connection refused" errorDetailed error message:
Couldn’t recover any analyses!
Reason: \[Errno 111\] Connection refused
*(from redmine: issue id 1241, created on 2012-11-08 by root, closed on 2013-01-14)*
* Changesets:
* Revision 1173 by Marcel Rieger o...Detailed error message:
Couldn’t recover any analyses!
Reason: \[Errno 111\] Connection refused
*(from redmine: issue id 1241, created on 2012-11-08 by root, closed on 2013-01-14)*
* Changesets:
* Revision 1173 by Marcel Rieger on 2013-01-14T13:03:17Z:
```
Fix #1241. Hide analysis dashboard due to unresolvable error.
```
* Revision 1173 by Marcel Rieger on 2013-01-14T13:03:17Z:
```
Fix #1241. Hide analysis dashboard due to unresolvable error.
```0.5https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/222Implement authentication for tests2019-05-20T17:09:09+02:00Benjamin FischerImplement authentication for testsRemove “if self.\_user and self.\_password:”, i.e. don’t allow
authentication with None
*(from redmine: issue id 1171, created on 2012-09-05 by root, closed on 2013-01-14)*Remove “if self.\_user and self.\_password:”, i.e. don’t allow
authentication with None
*(from redmine: issue id 1171, created on 2012-09-05 by root, closed on 2013-01-14)*0.5https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/201Loggingsystem2019-05-20T17:09:13+02:00Benjamin FischerLoggingsystemImplement a “multi”-logging system, to log (optional):
- server information
- user information
- errors on client/server side
- rpc system
- batch system
Part of this information maybe useful for monitoring.
*(from redmine:...Implement a “multi”-logging system, to log (optional):
- server information
- user information
- errors on client/server side
- rpc system
- batch system
Part of this information maybe useful for monitoring.
*(from redmine: issue id 1109, created on 2012-08-06 by root, closed on 2013-01-15)*0.5https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/195Analysis Designer Module Option Menu2019-05-20T17:09:16+02:00Benjamin FischerAnalysis Designer Module Option MenuA few features on the option menu of the modules in the AD could be
improved to enhance usability:
\- when renaming, insert the current name in the text field for the new
name (in case the user just wants to change the name, e.g. a numb...A few features on the option menu of the modules in the AD could be
improved to enhance usability:
\- when renaming, insert the current name in the text field for the new
name (in case the user just wants to change the name, e.g. a number)
\- offer a way to open the script of a module (pymodule, pyswitch,
pydecide, pyanalyse, pygenerator) from the AD (e.g. open script button
or an open button next to the filename option)
\- save dialogue of FileOutput
\- save analysis output to output folder or temp folder to keep user
folder clean (e.g. default output folder in user folder)
- implement creation of skeleton to support analysis creation online.
*(from redmine: issue id 1076, created on 2012-07-12 by root, closed on 2012-11-16)*0.5https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/186Use original user IP instead of REMOTE_ADDR when running in proxy mode.2019-05-20T17:09:17+02:00Benjamin FischerUse original user IP instead of REMOTE_ADDR when running in proxy mode.When Cherrypy runs behind a front-server (e.g. Apache) the user IP is
not
represented by the header entry “REMOTE\_ADDR” anymore. One should use
“X-Forwarded-For” or “HTTP-X-FORWARDED-FOR” instead.
see http://www.xinotes.org/notes/n...When Cherrypy runs behind a front-server (e.g. Apache) the user IP is
not
represented by the header entry “REMOTE\_ADDR” anymore. One should use
“X-Forwarded-For” or “HTTP-X-FORWARDED-FOR” instead.
see http://www.xinotes.org/notes/note/770/ for details.
*(from redmine: issue id 1042, created on 2012-06-02 by root, closed on 2013-01-07)*0.5https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/328file selector add menut entry not a function2019-05-20T16:26:09+02:00Benjamin Fischerfile selector add menut entry not a functionWhen pressing ‘Open file’, ‘save as’ or ‘save output as’ the file
selector should show. Instead an error ‘TypeError: self.addMenuEntry is
not a function’ in extension.js line 221 is thrown. The execute and save
button work just fine, so ...When pressing ‘Open file’, ‘save as’ or ‘save output as’ the file
selector should show. Instead an error ‘TypeError: self.addMenuEntry is
not a function’ in extension.js line 221 is thrown. The execute and save
button work just fine, so there is probably an error with the file
selector.
*(from redmine: issue id 1653, created on 2014-04-08 by root, closed on 2014-04-08)*
* Changesets:
* Revision 1241 by Martin Urban on 2014-04-08T11:57:32Z:
```
File: Fix funny circles around select box, fix #1653
```
* Revision 1241 by Martin Urban on 2014-04-08T11:57:32Z:
```
File: Fix funny circles around select box, fix #1653
```0.98https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/326Safe File2019-05-20T17:08:47+02:00Benjamin FischerSafe Filectrl+s wird nicht abgefangen und öffnet die Speicherfunktion des
Browsers
*(from redmine: issue id 1651, created on 2014-04-07 by root, closed on 2014-04-08)*
* Changesets:
* Revision 1233 by Thorben Quast on 2014-04-08T09:28:49Z:
...ctrl+s wird nicht abgefangen und öffnet die Speicherfunktion des
Browsers
*(from redmine: issue id 1651, created on 2014-04-07 by root, closed on 2014-04-08)*
* Changesets:
* Revision 1233 by Thorben Quast on 2014-04-08T09:28:49Z:
```
code editor: fix shorcuts, fix #1651.
```
* Revision 1233 by Thorben Quast on 2014-04-08T09:28:49Z:
```
code editor: fix shorcuts, fix #1651.
```0.98https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/323Submenus of the extensions are not touch compatible2019-05-20T17:08:47+02:00Benjamin FischerSubmenus of the extensions are not touch compatibleSubmenus of the extensions are not touch compatible, e.g. clicking on
the menu “change view” in the filebrowser pops up the submenu as long as
you hold your finger on “change view”. After releasing your finger the
submenu disappears too....Submenus of the extensions are not touch compatible, e.g. clicking on
the menu “change view” in the filebrowser pops up the submenu as long as
you hold your finger on “change view”. After releasing your finger the
submenu disappears too.
*(from redmine: issue id 1646, created on 2014-04-07 by martin.urban, closed on 2014-04-09)*0.98https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/451Editor: 2 Bugs in modification check2019-05-20T16:27:29+02:00Benjamin FischerEditor: 2 Bugs in modification check1. EVERY time the content has been modified, the confirm window (—&gt;
screenshot) shows up. This should only happen when the modification has
been made outside the editor instance.
2. Removal of files is not detected: Files that are op...1. EVERY time the content has been modified, the confirm window (—>
screenshot) shows up. This should only happen when the modification has
been made outside the editor instance.
2. Removal of files is not detected: Files that are opened within an
editor instance may be deleted without an appropriate message by (the at
this point minimized) editor.
*(from redmine: issue id 1921, created on 2014-10-12 by root, closed on 2014-10-12)*
* Changesets:
* Revision 1625 by Benjamin Fischer on 2014-10-12T16:26:59Z:
```
Fixing saving in codeeditor & fix selfcleanup of watches. fix #1921
```
* Revision 1625 by Benjamin Fischer on 2014-10-12T16:26:59Z:
```
Fixing saving in codeeditor & fix selfcleanup of watches. fix #1921
```
* Uploads:
* ![Reload_after_save](/uploads/a66c53bbd9398530f4345d722d7da1c4/Reload_after_save.png)1.0Benjamin FischerBenjamin Fischerhttps://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/449Marking text in the execute line of the codeeditor2019-05-20T17:08:32+02:00Benjamin FischerMarking text in the execute line of the codeeditorMarking text with the mouse in the execution command line of the
codeeditor is impossible, most probably due to the tooltip.
*(from redmine: issue id 1919, created on 2014-10-11 by martin.urban, closed on 2014-10-12)*
* Changesets:
...Marking text with the mouse in the execution command line of the
codeeditor is impossible, most probably due to the tooltip.
*(from redmine: issue id 1919, created on 2014-10-11 by martin.urban, closed on 2014-10-12)*
* Changesets:
* Revision 1624 by Benjamin Fischer on 2014-10-12T14:43:58Z:
```
Multiple fixes for the codeditor. fix #1918 & fix #1919
```
* Revision 1624 by Benjamin Fischer on 2014-10-12T14:43:58Z:
```
Multiple fixes for the codeditor. fix #1918 & fix #1919
```1.0https://git.rwth-aachen.de/3pia/vispa/vispa-web/-/issues/447Codeeditor compile and execute C++ files2019-05-20T17:08:32+02:00Benjamin FischerCodeeditor compile and execute C++ filesWhen writing a C<span class="underline"></span> file and compiling it
with the command *g<span class="underline"></span> -o out %file*
everything works fine. But for executing and compiling one has to use
*g<span class="underline"></span...When writing a C<span class="underline"></span> file and compiling it
with the command *g<span class="underline"></span> -o out %file*
everything works fine. But for executing and compiling one has to use
*g<span class="underline"></span> -o out %file && ./out*. This leads to
an error that the file && is unknown. In the default case the execute
button is not an execute button but only a compile button.
Furthermore the default output file is too long: %file\_compiled.out. In
linux the default output of g<span class="underline"></span> is called
a.out
*(from redmine: issue id 1917, created on 2014-10-11 by martin.urban, closed on 2014-10-12)*1.0