Uploaded image for project: 'YADE - Yet Another Data Exchange Tool'
  1. YADE - Yet Another Data Exchange Tool
  2. YADE-442

YADE does not transfer files with file names that contain diacritics such as é

    XMLWordPrintable

Details

    • Fix
    • Status: Known Issue (View Workflow)
    • Minor
    • Resolution: Works as designed
    • 1.9, 1.10, 1.11
    • 1.11.5
    • YADE JITL Jobs
    • None

    Description

      Current Situation

      • If a file name contains a diacritic character such as é and the YADE file_spec parameter of a transfer matches the file name then an error can occur:
        2017-10-20 14:17:56.557+0200 [ERROR]  (Task NPL/Job_FTP_A_NAS_NPL:77488) COM-80020009  Ausnahmefehler aufgetreten. [step] [] [Z-JAVA-105  Java exception com.sos.JSHelper.Exceptions.JobSchedulerException: SOSVfs_E_226: .. file '/home/test/input/test_?.txt' does not exist., method=spooler_process()Z [], in Remote_module_instance_server::step], method=call
        
      • This happens for SFTP servers that do not return file names with an UTF-8 encoding but with individual encodings such as ISO-8859-1.

      Desired Behaviour

      • File names that contain characters in ISO-8859-1 encoding should be transferred.

      Maintainer Notes

      • The YADE client works as designed as it expects an SFTP server to provide file names in UTF-8 if not otherwise requested by a client. This behavior is specified with draft-ietf-secsh-filexfer-13 - SSH File Transfer Protocol..
      • This problem has not been reported for Unix-based SFTP servers that usually return file names in UTF-8. For Windows-based SFTP servers the respective settings to return UTF-8 file names should be activated.

      Attachments

        Activity

          People

            re Robert Ehrlich
            ur Uwe Risse
            Mahendra Patidar Mahendra Patidar
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: