Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Eng 3068 create node result qet routes for metrics and checks #1403

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

eunice-chan
Copy link
Contributor

Describe your changes and why you are making these changes

Add result history routes for checks and metrics for use in the history display status bug (ENG-2578).

Tested in test_reads.py

Related issue number (if any)

ENG 3068
ENG-2578

Checklist before requesting a review

  • I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
  • I have performed a self-review of my code.
  • [N/A] I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
  • If this is a new feature, I have added unit tests and integration tests.
  • I have run the integration tests locally and they are passing.
  • I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
  • [N/A] All features on the UI continue to work correctly.
  • Added one of the following CI labels:
    • run_integration_test: Runs integration tests
    • skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

@eunice-chan eunice-chan added the run_integration_test Triggers integration tests label Jun 2, 2023
@eunice-chan eunice-chan requested a review from likawind June 2, 2023 21:33
}

responses := make([]response.OperatorWithArtifactResultNode, 0, len(results))
for dbDagId, nodeResults := range nodeResultByDagId {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Try to consolidate these repeating parts. We can file a task if the solution is not immediately clear

Copy link
Contributor

@likawind likawind left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work, a couple nits but I think the routes are good to go!

Copy link
Contributor

@likawind likawind left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work, a couple nits but I think the routes are good to go!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
run_integration_test Triggers integration tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants