update the distinct active state for the Job and Job Sets tab#4887
update the distinct active state for the Job and Job Sets tab#4887
Conversation
5fb438c to
5877261
Compare
Greptile SummaryThis PR adds a visible active state to the Jobs and Job Sets nav buttons using a theme-aware CSS custom property (
Confidence Score: 4/5One P1 bug makes the active indicator always visible on the Jobs button — needs the A single P1 logic bug: the missing internal/lookoutui/src/app/NavBar.tsx — the Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A["NavBar renders"] --> B["StyledAppBar sets --nav-active-bg\nvia alpha(contrastText, 0.33)"]
B --> C["NavLinkButton wraps NavLink"]
C --> D{"NavLink prefix match\nagainst current URL"}
D -->|"JOBS = '/' matches ALL routes\n(missing end prop)"| E["❌ .active class always added\nto Jobs button"]
D -->|"JOB_SETS = '/job-sets'\nonly matches /job-sets"| F["✅ .active class added correctly"]
E --> G[".toolbar a.MuiButton-root.active\napplies --nav-active-bg + bold"]
F --> G
G --> H["Jobs button always highlighted\nregardless of current page"]
|
Signed-off-by: Yasmine Hines <yhines004@gmail.com>
…off-by: Yasmine Hines yasmine.hines@nmc2.ai Signed-off-by: Yasmine Hines <yhines004@gmail.com>
Drops the failure_info jsonb column from job_run. Nothing writes or reads it after #4843 and #4853, and the column was never populated in production outside the opt-in flag path anyway. Also drops the unused FailureInfo field from the queryapi sqlc model. Only merge after #4843 and #4853 have been deployed long enough that we are sure no consumer still depends on the column. Signed-off-by: Dejan Zele Pejchev <pejcev.dejan@gmail.com> Signed-off-by: Yasmine Hines <yhines004@gmail.com>
<!-- Thanks for sending a pull request! Here are some tips for you: --> #### What type of PR is this? #### What this PR does / why we need it Updating Lookout to include a hot/cold flag for utilizing the hot/cold partitioned jobs database, as well as updating the lookout pruner to only prune jobs from the `job_terminated` table when hot/cold is in use #### Which issue(s) this PR fixes <!-- *Automatically closes linked issue when PR is merged. Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. _If PR is about `failing-tests or flakes`, please post the related issues/tests in a comment and do not use `Fixes`_* --> Fixes # #### Special notes for your reviewer --------- Signed-off-by: David Slear <david_slear@yahoo.com> Signed-off-by: Yasmine Hines <yhines004@gmail.com>
<!-- Thanks for sending a pull request! Here are some tips for you: --> #### What type of PR is this? feature / observability #### What this PR does / why we need it Adds a Prometheus counter metric to the lookout ingester to track job state updates processed by UpdateJobs(). The metric (`lookout_ingester_job_state_updates_total`) is labeled by state, allowing operators to observe transition rates and specifically monitor terminal state updates, which trigger cross-partition row movement in the Lookout database. Also fixes error categorization schema in `_local/executor` configs that was broken by a prior change. #### Special notes for your reviewer The `terminal_state_updates_total` counter was initially added as a standalone metric but was removed in favor of deriving it via PromQL from the per-state counter (sum by state where state is terminal). --------- Signed-off-by: Ian Hockett <ian@hockett.net> Signed-off-by: Yasmine Hines <yhines004@gmail.com>
Signed-off-by: Yasmine Hines <yhines004@gmail.com>
7467ad3 to
60bc2e1
Compare
What type of PR is this?
Enhancement
What this PR does / why we need it
This PR give the button/tab for Job and Job Sets a distinct active state when one of them are selected. We need this to give a distinctive state of which tab is active.
Which issue(s) this PR fixes
Fixes #
Special notes for your reviewer