Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-15769

Better error message required for no input data

    XMLWordPrintable

Details

    • Story
    • Status: Done
    • Resolution: Done
    • None
    • pipe_drivers
    • None
    • Architecture

    Description

      When running the `construct*.py` scripts, if there is no input data (e.g. when the ingest has failed), the error one gets tends to be a division by zero from the zero-length of the refList. This is more confusing to newbies and people unfamiliar with this part of the stack that one might expect, and is worth fixing I think. A simple check that one isn't operating on no data before going ahead should suffice I think.

      Attachments

        Activity

          ktl Kian-Tat Lim added a comment -

          Added a couple of error checks.

          ktl Kian-Tat Lim added a comment - Added a couple of error checks.

          Looks great!

          mfisherlevine Merlin Fisher-Levine added a comment - Looks great!
          ktl Kian-Tat Lim added a comment -

          Passes Jenkins, although likely untested except flake8; merged in f9cb114.

          ktl Kian-Tat Lim added a comment - Passes Jenkins, although likely untested except flake8; merged in f9cb114.

          People

            ktl Kian-Tat Lim
            mfisherlevine Merlin Fisher-Levine
            Merlin Fisher-Levine
            Kian-Tat Lim, Merlin Fisher-Levine
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Jenkins

                No builds found.