feat(ui): show failure reason inline in the queue jobs list - #51
Open
omarzeineddine-ai wants to merge 1 commit into
Open
feat(ui): show failure reason inline in the queue jobs list#51omarzeineddine-ai wants to merge 1 commit into
omarzeineddine-ai wants to merge 1 commit into
Conversation
The 'needs attention' flow lands on a queue's failed jobs, but the list only showed name/id/status — you had to open each job to see why it failed. Render the truncated failedReason on failed rows, using the same treatment as the global runs list. Closes pontusab#31
|
@omarzeineddine-ai is attempting to deploy a commit to the Pontus Abrahamsson's projects Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Closes #31
The needs attention section links straight to a queue's failed job runs, but the list there only shows name/id/status — you have to click into each job to see what actually failed. The global Runs view already renders the truncated
failedReasoninline on failed rows.Solution
Render the same inline error treatment in the queue page's job list: failed rows show the truncated
failedReason(80 chars, full message on hover viatitle), styled and truncated identically to the global runs list.No API changes needed — the queue jobs endpoint already returns
failedReason(jobToInfoincludes it in bothlistandfullmodes), so this is an 8-line UI change reusing the existing pattern.Verification
GET /api/queues/:name/jobs?status=failedreturnsfailedReasonfor each row the UI renders.tsc --noEmit,biome check, and the vite UI build all pass.No unit test added: the change is presentation-only, reusing markup already exercised by the runs page, and the repo has no component test infrastructure.