deepujain commented on PR #64374: URL: https://github.com/apache/airflow/pull/64374#issuecomment-4149529179
Follow-up after investigating the current failing checks: - I found one branch-specific regression in this change set: on stale DAG detail pages I had also hidden the manual `Trigger DAG` button in `DetailsLayout`, which is broader than the intended UX change. This push restores the trigger entry point while keeping the deactivated badge and hiding the stale-only pause / next-run affordances. - I also fixed the formatting drift on the touched UI files so the local static checks are clean again. Local validation rerun on this head: - `npm run test -- Header.test.tsx` - `pnpm exec eslint src/components/DagDeactivatedBadge.tsx src/layouts/Details/DagBreadcrumb.tsx src/layouts/Details/DetailsLayout.tsx src/pages/Dag/Header.tsx src/pages/Dag/Header.test.tsx` - `pnpm exec tsc --noEmit -p tsconfig.app.json` - `pnpm exec prettier --write src/components/DagDeactivatedBadge.tsx src/layouts/Details/DagBreadcrumb.tsx src/layouts/Details/DetailsLayout.tsx src/pages/Dag/Header.tsx src/pages/Dag/Header.test.tsx public/i18n/locales/en/dag.json` I force-pushed the existing PR branch so CI reruns on this narrower behavior. The previous Chromium / Firefox failures were still broad (`backfill`, `requiredAction`, `xcoms`, and task-instance flows), so this rerun should tell us whether the stale-DAG action suppression was part of that fallout or whether there is still unrelated noise in those jobs. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
