Uploaded image for project: 'Aurora'
  1. Aurora
  2. AURORA-1871

Client should reject tasks with duplicate process names

    XMLWordPrintableJSON

Details

    • Task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • Client
    • None

    Description

      If a user creates a job that contains tasks with the same process name, that info is happily passed on to thermos, which will happily run one of those processes, but maybe display a separate one in the UI. In general the behavior in this case is non-deterministic and can lead to hard to track down bugs.

      We should just short circuit and fail in the client if we detect multiple processes with the same name.

      Attachments

        Activity

          People

            Unassigned Unassigned
            joshua.cohen Joshua Cohen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: