fix: Add auto-refresh functionality to Required Actions page#56404
fix: Add auto-refresh functionality to Required Actions page#56404pierrejeambrun merged 7 commits intoapache:mainfrom
Conversation
airflow-core/src/airflow/ui/src/pages/HITLTaskInstances/HITLTaskInstances.tsx
Outdated
Show resolved
Hide resolved
|
@bbovenzi thanks for the suggestion! I switched the fixed refetch interval to a conditional one: |
airflow-core/src/airflow/ui/src/pages/HITLTaskInstances/HITLTaskInstances.tsx
Outdated
Show resolved
Hide resolved
|
Thanks @bbovenzi , I removed effectiveResponseReceived only use the query.state.data |
pierrejeambrun
left a comment
There was a problem hiding this comment.
A couple nit to fix before we can merge.
airflow-core/src/airflow/ui/src/pages/HITLTaskInstances/HITLTaskInstances.tsx
Outdated
Show resolved
Hide resolved
airflow-core/src/airflow/ui/src/pages/HITLTaskInstances/HITLTaskInstances.tsx
Outdated
Show resolved
Hide resolved
pierrejeambrun
left a comment
There was a problem hiding this comment.
CI is still failing, do you mind fixing it so we can merge the PR.
No problem, I'll try! Thanks! |
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker 9adb256 v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
…56404) * Add auto-refresh functionality to Required Actions page * switch refresh interval * remove dependance of effectiveResponseReceived * remove typescript error and comment * fix static check error * fix ts-compile-lint-ui error --------- Co-authored-by: Brent Bovenzi <brent@astronomer.io> (cherry picked from commit 9adb256)
|
Manual backport #57207 |
|
Thanks for everyone! |
related: #56081
We don't need to press refresh-key manually.
thanks for review.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.