-
Notifications
You must be signed in to change notification settings - Fork 18
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
base: main
Are you sure you want to change the base?
Eng 3068 create node result qet routes for metrics and checks #1403
Conversation
…reate-nodemetricresultsgetquery-nodecheckresultsgetquery
} | ||
|
||
responses := make([]response.OperatorWithArtifactResultNode, 0, len(results)) | ||
for dbDagId, nodeResults := range nodeResultByDagId { |
There was a problem hiding this comment.
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
There was a problem hiding this 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!
There was a problem hiding this 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!
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
python3 scripts/run_linters.py -h
for usage).run_integration_test
: Runs integration testsskip_integration_test
: Skips integration tests (Should be used when changes are ONLY documentation/UI)