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 2332 Differentiate warning between pending and upstream failure #986

Merged
merged 3 commits into from
Feb 14, 2023

Conversation

eunice-chan
Copy link
Contributor

Describe your changes and why you are making these changes

Correct artifact messaging.
Unable to reproduce other observations: https://linear.app/aqueducthq/issue/ENG-2332#comment-a9e27957

Related issue number (if any)

ENG 2332

Demo (if any)

Update messaging if input is pending for metric & operator artifacts:
Screen Shot 2023-02-10 at 8 13 17 PM
image

Messaging remains correct in failure case:
image

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.
  • I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
  • [N/A] If this is a new feature, I have added unit tests and integration tests.
  • [N/A] 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).
  • 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 skip_integration_test Skips required integration test (only documentation/UI changes) label Feb 11, 2023
@@ -205,10 +205,69 @@ const ArtifactDetailsPage: React.FC<ArtifactDetailsPageProps> = ({
const inputs = mapOperators([artifact.from]);
const outputs = mapOperators(artifact.to ? artifact.to : []);

let upstream_pending = false;
inputs.some((operator) => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Just curious, why are you using some here instead of filter?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I only want to check whether any of the upstream operators are pending. some terminates on first True whereas filter will create another array with all that matches the criteria. We might want to use filter in the future if we want to display something for the pending operators but for now, I am not doing that.

@eunice-chan eunice-chan merged commit 7935a78 into main Feb 14, 2023
@vsreekanti vsreekanti deleted the eng-2332-clicking-on-pending-nodes-leads-to branch April 4, 2023 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
skip_integration_test Skips required integration test (only documentation/UI changes)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants