TransferZeroByteFile false|strict|relaxed functionality is broken

CurrentSituation

• TransferZeroByteFile = false
  • When YADE is configured with this setting then the files with zero byte size should be transferred if at least one of the selected files is more than zero byte in size.
    • This functionality is broken:
      • YADE reports all files as the zero byte files (file size independent) and aborts the transfer.
• TransferZeroByteFile = strict
  • When YADE is configured with this setting then the files with zero byte size will not be transferred. An error will be raised if any zero byte file is found.
    • This functionality is broken:
      • YADE reports all files as the zero byte files (file size independent) and aborts the transfer.
• TransferZeroByteFile = relaxed
  • When YADE is configured with this setting then the files with zero byte size will not be transferred. However, no error will be raised if this results in no files being transferred.
    • This functionality is broken:
      • YADE handles all files as the zero byte files (file size independent) and will not transfer any file.

Desired Behavior

• The TransferZeroByteFile functionallity should work as expected.
• Improved extended INFO Logging for skipped transfers.

Applicable JobScheduler releases
A patch is available for download with JobScheduler releases:

• JobScheduler 1.13.4
  • Download the patch patch-20200710-YADE-562.1.13.4.zip
    • Extract the patch-20200710-YADE-562.1.13.4.zip to any location
    • Copy patch-20200710-YADE-562.1.13.4.jar to
      • {$scheduler_home}/lib/patches
    • Perform a restart