-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
Hide Irrelevant Dag Processor from Cluster Activity Page #33611
Conversation
@bbovenzi how can I prevent this error from occurring in the
|
Look at |
Care to rebase? Not sure why some images aren't building correctly. |
I rebased. We had a "botocore" causing backtracking issues (solved today with #33649 |
replacing bottom margin with a top margin
removed bottom margin from triggerer
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.
LGTM thank you!
Re-running the failed job, should be green
* first commit * refactoring * adding undefined default * added logic to check if defined * refactored component * refactored not equal sign * refactored code for boolean type instead of string * refactored global variable. refactored conditional * pre-commit and linting fixes * updated jest-setup * updated jest-setup * precommit fix * Update Health.tsx replacing bottom margin with a top margin * Update Health.tsx removed bottom margin from triggerer (cherry picked from commit c055e1d)
Users should not see the Dag Processor health on the Cluster Activity page if
standalone_dag_processor=False
.closes: #33497