Known issues

  1. Known issues
    1. Current issues
      1. Major
      2. Medium
      3. Minor

Current issues

Major

  • Grisu can't handle some special characters in filenames (like #). If a file with such a filename exists, Grisu will only display an empty directory.
  • When used on Linux and with Java version 6: there is a bug in the linux implementation of Java that disables all input from keyboard/mouse if a combobox is open and the application waits for input. This can happen if the user changes to a different site (whose gridftp server doesn't work) on the file management panel. Only solution is to switch to a virtual console and kill the java process that runs the Swing client.
  • Sometimes, file upload stops working during stop submission and keeps failing until the Grisu Swing client is restarted. Since this error is not reproducable (yet), the only workaround we can offer is a restart.
  • File transfer very slow for a big number of smaller files.
  • Directory listing very slow for directories with lots of files. This is fixed in the current version of the code and should be fixed in the next release.
  • Connections via authenticated http proxies don't work.

Medium

  • Grisu does not check how big files are that are being viewed by the embedded viewers. That can cause Grisu to hang.
  • Grisu does not check whether a file already exists on the location you want to copy it. It just overwrites it.
  • There are problems with Swing and CentOS 64bit. Sometimes users can't type into the password field. The workaround appears to be clicking in other text fields and then return to the password field.

Minor

  • In some networks the linux version of the Grisu swing client stalls after clicking the login button. This is due to a connection to ca.apac.edu.au on port 80. Setting up a firewall rule to reject these packets is a work-around for this.
  • Because of some restrictions of the jsdl format, Grisu can only submit 1 cpu "single" jobs and ≥2 cpu "mpi" jobs. It's not possible to submit a 1-cpu "mpi" job, neither is it possible to submit a 2-cpu "single" job, but that makes even less sense anyway…
  • Local backend staging in of local files doesn't work on Windows.
  • After job submission, if a user navigates to the job directory using the "File management" tab, it'll show an outdated view. The user has to refresh the directory manually. This is not really a bug, but users need to be aware of this.
  • The client does not create a proxy that is only obtainable by a APACGrid machine. That does not limit functionality, but security…
  • The progress of how much of a file transfer is already finished does not show the exact percentage.
  • Some of the pop-up windows pop up in the background and you have to minimize all other windows first before you are able to see them.
  • The commandline client doesn't work if the DISPLAY environment variable is set to something that can't be accessed. As a workaround, just unset the DISPLAY variable.
  • The file transfer control feature is not really intuitive yet.