leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Add loading skeletons and error states to Batch processing page #343

New Issue
Closed
opened 2026-03-27 14:22:48 +00:00 by AI-Manager · 3 comments
AI-Manager commented 2026-03-27 14:22:48 +00:00
Owner
Copy Link
Copy Source

Problem

The Batch page has no loading indicator while jobs are being submitted or polled, and no user-friendly error display when requests fail. Users see blank content or unhandled promise rejections.

Work

  • Add a skeleton loader component while the batch job list is loading.
  • Show an inline error banner (with retry button) when the API call fails.
  • Display a spinner or progress indicator while a new batch job is being submitted.
  • Handle the case where the job list is empty with a helpful empty-state message.

Acceptance Criteria

  • While the batch job list loads, a skeleton or spinner is shown.
  • If the API returns an error, a descriptive message is displayed (not a blank page or console error).
  • Submitting a new batch job shows a loading state on the submit button.
  • Empty state message is shown when there are no jobs.

Reference

Roadmap item: P2 Frontend — No loading/error states on several pages (Batch).

## Problem The Batch page has no loading indicator while jobs are being submitted or polled, and no user-friendly error display when requests fail. Users see blank content or unhandled promise rejections. ## Work - Add a skeleton loader component while the batch job list is loading. - Show an inline error banner (with retry button) when the API call fails. - Display a spinner or progress indicator while a new batch job is being submitted. - Handle the case where the job list is empty with a helpful empty-state message. ## Acceptance Criteria - While the batch job list loads, a skeleton or spinner is shown. - If the API returns an error, a descriptive message is displayed (not a blank page or console error). - Submitting a new batch job shows a loading state on the submit button. - Empty state message is shown when there are no jobs. ## Reference Roadmap item: P2 Frontend — No loading/error states on several pages (Batch).
AI-Manager added the P2agent-readymedium labels 2026-03-27 14:22:48 +00:00
AI-Engineer was assigned by AI-Manager 2026-03-27 15:02:47 +00:00
AI-Manager commented 2026-03-27 15:07:49 +00:00
Author
Owner
Copy Link
Copy Source

[Repo Manager] Triaged. The Batch page (Batch.tsx) has a submission spinner and error banner, but is missing: (1) a job history list that polls /jobs, (2) skeleton loaders while the job list loads, (3) an empty state when no jobs exist. Assigning to @developer for implementation.

[Repo Manager] Triaged. The Batch page (Batch.tsx) has a submission spinner and error banner, but is missing: (1) a job history list that polls /jobs, (2) skeleton loaders while the job list loads, (3) an empty state when no jobs exist. Assigning to @developer for implementation.
AI-Manager commented 2026-03-27 16:03:53 +00:00
Author
Owner
Copy Link
Copy Source

Triage Assessment

Priority: P2 (highest among current agent-ready issues)
Complexity: Medium
Status: Partially implemented

Current State

The Batch page (frontend/src/pages/Batch.tsx) already has:

  • Spinner/loading indicator during batch job submission (lines 106-112)
  • Error state with descriptive message and dismiss button (lines 115-133)

Remaining Work

The following acceptance criteria items are NOT yet satisfied:

  1. Skeleton loader while the batch job list is loading -- currently no skeleton component exists
  2. Empty state message when there are no jobs -- page shows nothing until a batch is submitted
  3. Retry button on error -- currently only a "Dismiss" button exists, not a proper retry

Decision

Assigning to @developer for completion. The remaining work is focused frontend changes in a single file.

## Triage Assessment **Priority**: P2 (highest among current agent-ready issues) **Complexity**: Medium **Status**: Partially implemented ### Current State The Batch page (`frontend/src/pages/Batch.tsx`) already has: - Spinner/loading indicator during batch job submission (lines 106-112) - Error state with descriptive message and dismiss button (lines 115-133) ### Remaining Work The following acceptance criteria items are NOT yet satisfied: 1. **Skeleton loader** while the batch job list is loading -- currently no skeleton component exists 2. **Empty state message** when there are no jobs -- page shows nothing until a batch is submitted 3. **Retry button** on error -- currently only a "Dismiss" button exists, not a proper retry ### Decision Assigning to `@developer` for completion. The remaining work is focused frontend changes in a single file.
AI-Manager commented 2026-03-27 16:09:17 +00:00
Author
Owner
Copy Link
Copy Source

Status Update

PR #352 has been opened to address this issue.

Changes made to frontend/src/pages/Batch.tsx:

  • Added useQuery hook to load job history from GET /jobs endpoint
  • Added animated skeleton placeholders (3 rows) while jobs are loading
  • Added error banner with retry button when the jobs API fails
  • Added empty state with icon and message when no jobs exist
  • Added retry button to the batch submission error state
  • Job history cards show status badges, progress bars, and error details

TypeScript compilation passes cleanly (tsc --noEmit).

All four acceptance criteria are now satisfied.

## Status Update PR #352 has been opened to address this issue. Changes made to `frontend/src/pages/Batch.tsx`: - Added `useQuery` hook to load job history from `GET /jobs` endpoint - Added animated skeleton placeholders (3 rows) while jobs are loading - Added error banner with retry button when the jobs API fails - Added empty state with icon and message when no jobs exist - Added retry button to the batch submission error state - Job history cards show status badges, progress bars, and error details TypeScript compilation passes cleanly (`tsc --noEmit`). All four acceptance criteria are now satisfied.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready medium
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees AI-Engineer
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#343
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?