Uploaded image for project: 'Pegasus'
  1. Pegasus
  2. PM-1406

Better error logging when TC contains a bad PFN

    XMLWordPrintable

Details

    • Improvement
    • Status: Open
    • Minor
    • Resolution: Unresolved
    • 5.0.0, 4.9.3
    • None
    • Pegasus Planner
    • None

    Description

      When a bad PFN is entered into a TC, it should be clear to the user that this is invalid input based on error logs.

      Scenario:
      An entry in a TC has the following:
      tr script.sh {
          site local {
              pfn "script.sh" <--- should be $(pwd)/script.sh
              type "STAGEABLE"
          }
      }

      Expected Result:
      Some error message like "Transformation script.sh has invalid pfn: 'script.sh'"

      Actual Result:
      2019.10.28 15:08:49.916 PDT: [FATAL ERROR] [1] java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1967)

      Attachments

        Activity

          People

            vahi Karan Vahi
            tanaka Ryan Tanaka
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: