Hitl dashboard - extend API to support different pipeline, added traceback list view component

[mialsy]

Description

• Extend components / backend APIs to be able to display different pipeline.
• Added traceback list component.

Type of change

Please check the options that are relevant.

• Bug fix (non-breaking change that fixes an issue)
• Proposes a change (non-breaking change that isn't necessarily a bug)
• Refactor
• New feature (non-breaking change that adds a new functionality)
• Breaking change (fix or feature that would break some existing functionality downstream)
• This is a unit test
• Documentation only change
• Datasets Release
• Models Release

Type of requested review

• I want a thorough review of the implementation.
• I want a high level review.
• I want a deep design review.

Before and After

• Changed the get_jobs api to get_runs to make it consistent with wording at frontend
• Updated get run API, changes are highlighted as bellow
  • Before
    • get run takes no input, the code crawls all s3 object with patterns of batch id and return the batch ids as a list
  • After
    • get run takes input pipeline name, it reads s3 bucket and reads the corresponding file: {pipeline_name}_run_list; and only return the run corresponding to the input pipeline name.

Demo:

• View different pipeline
  -
• View traceback list
  -

Testing

Manually tested.

Checklist:

• I have performed manual end-to-end testing of the feature in my environment.
• I have added Docstrings and comments to the code.
• I have made changes to existing documentation where needed.
• I have added tests that show that the PR is functional.
• New and existing unit tests pass locally with my changes.
• I have added relevant collaborators to review the PR before merge.
• [Polymetis only] I ran on hardware (1) all scripts in tests/scripts, (2) asv benchmarks.

[facebook-github-bot]

Hi @mialsy!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!