labtasker-webui 0.1.1__tar.gz → 0.2.0__tar.gz

{labtasker_webui-0.1.1 → labtasker_webui-0.2.0}/.agents/sops/qa.md

@@ -37,6 +37,20 @@ LABTASKER_REAL_SERVER_URL=http://127.0.0.1:8000 uv run pytest -m integration tes
 Set `LABTASKER_REAL_SERVER_TOKEN` through an existing secure mechanism if needed; never
 paste it into committed scripts or captured shell output.
 
+To check a sibling Labtasker source checkout, run the isolated BFF contract test:
+
+```sh
+uv run --with ../labtasker/packages/labtasker-server pytest -q -s -m integration tests/test_upstream_source.py
+uv run --with-editable ../labtasker/packages/labtasker-server --with-editable ../labtasker/packages/labtasker-client pytest -q -s -m integration tests/test_upstream_source.py
+```
+
+These commands use temporary dependency overlays without changing the lockfile. The
+first checks the locked Client against the source Server; the second uses both source
+packages in editable mode. The test creates only a temporary database and synthetic Tasks/Workers,
+using in-process ASGI transport without connecting to a running instance. It covers
+pagination, filters, counts, observations, error forwarding and Task actions. The
+normal suite excludes it; without an installed Server it skips.
+
 ## Interaction review matrix
 
 | Area | Cases to verify |
@@ -44,7 +58,7 @@ paste it into committed scripts or captured shell output.
 | Layout | 1440×900 desktop, 900×600 short window, 390×700 narrow window; no document-level horizontal overflow |
 | Popups | Every edge; resize while open; many options; long names; internal scrolling; Escape, outside click and Tab |
 | Keyboard | Arrow keys/Home/End follow visible active option; Enter applies; IME Enter does not submit prematurely |
-| Filters | Dropdowns/presets immediate; text blur/Enter; clear; invalid input and correction; counts match applied selectors |
+| Filters | Dropdowns/presets immediate; text blur/Enter; clear; invalid input and correction; status cards respect applied name/expression but ignore the Status selector; list totals include Status |
 | Navigation | Queue → filter → drawer → back/forward; URL and visible state agree |
 | Selection | Empty/partial/all checkbox; sorting retains selection; filtering clears selection; append keeps existing selection |
 | Columns | Independent resize; double-click fit; drag order; missing JSON paths blank; path casing preserved; reload restoration |

{labtasker_webui-0.1.1 → labtasker_webui-0.2.0}/AGENTS.md

@@ -40,7 +40,7 @@
 - Preserve breadcrumbs and the compact, information-dense layout. Do not reintroduce a duplicate queue heading or large decorative spacing.
 - Queue layout and named views are scoped by connection identity **and** queue. Never reintroduce a global columns fallback.
 - Dropdowns and presets apply immediately. Text filters apply on Enter or leaving the input group; Apply is a fallback. Respect IME composition.
-- Counts describe the same applied selectors as the list. Sorting preserves selection; changing the filter range clears it.
+- Status card counts use applied Task name and filter expressions, ignoring the Status selector; list totals also include the selected Status. Sorting preserves selection; changing the filter range clears it.
 - Browser history restores queue, applied filters and drawer consistently. Partial selection uses the native checkbox `indeterminate` property.
 - Resizing changes only the chosen column. Double-click fits content. Reordering preserves paths and uses a drop line, not a shaded target row.
 - Every popup must fit the viewport, support scrolling and Escape/outside dismissal, and remain usable with keyboard navigation. Check Safari/WebKit focus behavior, not only Chromium.

{labtasker_webui-0.1.1 → labtasker_webui-0.2.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: labtasker-webui
-Version: 0.1.1
+Version: 0.2.0
 Summary: A focused web interface for Labtasker v2
 Project-URL: Homepage, https://github.com/luocfprime/labtasker-webui
 Project-URL: Repository, https://github.com/luocfprime/labtasker-webui
@@ -11,6 +11,7 @@ Requires-Python: >=3.11
 Requires-Dist: fastapi<1,>=0.115
 Requires-Dist: httpx[socks]<1,>=0.27
 Requires-Dist: labtasker-client<3,>=2.1
+Requires-Dist: packaging<27,>=24
 Requires-Dist: uvicorn<1,>=0.34
 Provides-Extra: local
 Requires-Dist: labtasker-client<3,>=2.1; extra == 'local'
@@ -28,7 +29,11 @@ workspace, with reusable views for different experiments.
 The key features are:
 
 - **Queue progress at a glance:** Track pending, running, succeeded, failed, and
-  cancelled Tasks. Status counts follow the same filters as the Task list.
+  cancelled Tasks. Status counts follow the applied Task name and advanced filter, across all statuses; the Status selector narrows only the Task list and its total.
+- **Routes and Workers:** Collapse route navigation when you need more table space.
+  Inspect Idle/Busy Worker counts and last-seen reports; include inactive routes when
+  reviewing historical work. These features require Server 2.2 or later; Worker
+  reports require Workers that support observations.
 - **Flexible result exploration:** Filter Task fields and nested values, or add
   custom columns such as `args.test_num` and `result.succ_rate`. Resize, reorder,
   and double-click columns to fit their contents.
@@ -68,6 +73,11 @@ Choose a connection type on the connection page:
   `.` refers to the WebUI process's working directory. Local attachment uses the
   project's Unix socket and requires POSIX and a loopback bind.
 
+If a business response reports a Server older than the installed Labtasker Client,
+WebUI displays a dismissible upgrade warning. It adds no version-check request
+and does not block browsing or actions. Servers that omit their version do not
+trigger the warning. Reloading or reconnecting resets dismissal.
+
 Open a Queue, then filter its Tasks:
 
 ```python
@@ -175,3 +185,13 @@ and installation of the built package without Node.js.
 ## License
 
 [Apache-2.0](https://github.com/luocfprime/labtasker-webui/blob/main/LICENSE), matching Labtasker.
+
+### Search Task names
+
+The Task name input supports case-insensitive subsequence search: `tr ev` or
+`ev tr` finds `train_model_eval`. Every whitespace-separated word must match.
+Press Enter or leave the input to apply; clearing it removes the name restriction.
+For a strict name match, use `name == "train_model_eval"` in Advanced filter.
+The Server applies the same search to the Task list and counts across the Queue,
+with the existing sorting preserved. This requires a Server supporting
+`name_fuzzy`; saved Task name inputs also use fuzzy matching.

{labtasker_webui-0.1.1 → labtasker_webui-0.2.0}/README.md

@@ -10,7 +10,11 @@ workspace, with reusable views for different experiments.
 The key features are:
 
 - **Queue progress at a glance:** Track pending, running, succeeded, failed, and
-  cancelled Tasks. Status counts follow the same filters as the Task list.
+  cancelled Tasks. Status counts follow the applied Task name and advanced filter, across all statuses; the Status selector narrows only the Task list and its total.
+- **Routes and Workers:** Collapse route navigation when you need more table space.
+  Inspect Idle/Busy Worker counts and last-seen reports; include inactive routes when
+  reviewing historical work. These features require Server 2.2 or later; Worker
+  reports require Workers that support observations.
 - **Flexible result exploration:** Filter Task fields and nested values, or add
   custom columns such as `args.test_num` and `result.succ_rate`. Resize, reorder,
   and double-click columns to fit their contents.
@@ -50,6 +54,11 @@ Choose a connection type on the connection page:
   `.` refers to the WebUI process's working directory. Local attachment uses the
   project's Unix socket and requires POSIX and a loopback bind.
 
+If a business response reports a Server older than the installed Labtasker Client,
+WebUI displays a dismissible upgrade warning. It adds no version-check request
+and does not block browsing or actions. Servers that omit their version do not
+trigger the warning. Reloading or reconnecting resets dismissal.
+
 Open a Queue, then filter its Tasks:
 
 ```python
@@ -157,3 +166,13 @@ and installation of the built package without Node.js.
 ## License
 
 [Apache-2.0](https://github.com/luocfprime/labtasker-webui/blob/main/LICENSE), matching Labtasker.
+
+### Search Task names
+
+The Task name input supports case-insensitive subsequence search: `tr ev` or
+`ev tr` finds `train_model_eval`. Every whitespace-separated word must match.
+Press Enter or leave the input to apply; clearing it removes the name restriction.
+For a strict name match, use `name == "train_model_eval"` in Advanced filter.
+The Server applies the same search to the Task list and counts across the Queue,
+with the existing sorting preserved. This requires a Server supporting
+`name_fuzzy`; saved Task name inputs also use fuzzy matching.

labtasker_webui-0.2.0/docs/reference/specification.md

@@ -0,0 +1,245 @@
+# WebUI specification
+
+```text
+Browser (React, Query, Table)
+  -> same-origin /api/webui/* (FastAPI BFF)
+     -> HTTP Labtasker v2 Server, or existing project's Unix socket
+```
+
+The BFF owns upstream credentials, session cookies, origin validation and destructive
+operation snapshots. The UI observes Tasks and supports cancel, requeue and selected-ID
+deletion; it does not submit/edit Tasks. Local attachment discovers and uses the existing
+socket without managing the Labtasker process or opening its database.
+
+## Server version warnings
+
+The BFF observes `Labtasker-Server-Version` on ordinary upstream `/api/`
+responses, including errors and empty successes, for both HTTP and local
+connections. Existing connection verification stays unchanged; version warnings
+add no upstream requests. Health/schema responses are not version observations.
+
+On a BFF response that observed an upstream business response, it sends
+`Labtasker-Client-Version` (the installed `labtasker-client` version),
+`Labtasker-Server-Version` (normalized PEP 440 version, or an empty value when
+unknown), and `Labtasker-Server-Upgrade-Recommended` (`true` or `false`). Missing,
+invalid, or longer-than-128-character upstream versions are unknown. Comparison
+uses PEP 440 ordering, including patch and prerelease differences; the WebUI's
+independent package version is not compared to the Server. Version observations
+are request-local and must not leak across sessions or credentials. No tokens
+are added to these headers; upstream payloads and errors remain unchanged.
+
+The browser displays a compact, nonblocking, dismissible warning above the
+workspace when the Server is older. It recommends upgrading to the Client version
+or later without claiming that a particular operation is incompatible. Repeated
+responses for a dismissed version pair do not redisplay it. A different older
+version pair can warn again; an equal, newer, or unknown observation clears the
+visible warning. Responses without an upstream observation leave it unchanged.
+Observations and dismissal are memory-only and reset on reload/reconnection.
+Neither credentials nor version observations are written to the profile.
+
+## State
+
+| State | Owner and persistence |
+| --- | --- |
+| Connection URL/local project | Backend profile in WebUI working directory |
+| Bearer token | Backend only; separate owner-only `webui-token` file |
+| Queue, applied selectors, drawer Task ID | URL/history plus React state |
+| Current working column layout | Connection + queue scope; browser and profile |
+| Named data view | Explicit snapshot scoped to connection + queue |
+| Task selection | Current workspace memory; exact Task IDs |
+| Pending profile write | Browser recovery record until the backend acknowledges saving |
+| Task data and counts | Query cache keyed by connection lifecycle, queue and applied selectors |
+
+A profile contains a map of UI settings; it is not itself a named data view. Views capture
+filters, sort order, visible/custom columns, order and widths. Layout edits do not mutate
+a named view until Save. The backend UI-key allowlist must remain consistent with frontend
+persistence keys; internal browser recovery keys must never enter profile API payloads.
+Saved-view change detection compares setting values rather than object key order.
+Older views without a route field are equivalent to an empty route selection, so
+applying or resetting them does not falsely report unsaved changes.
+
+Backend profile writes use atomic replacement and restrictive permissions. Failed writes
+must not be reported as persisted by a subsequent API read. Browser pending writes are
+retained across reload and merged before restoring older disk settings. Successful writes
+acknowledge only values actually sent, preserving newer edits queued during the request.
+Saves time out after 10 seconds and remain recoverable. Payloads above 60 KiB use normal
+fetch instead of the browser-limited keepalive transport; interrupted writes stay in the
+browser recovery record.
+
+Successful login clears query caches and reloads connection status before rebuilding
+the workspace. A new session must never expose the previous connection's cached Tasks,
+including when reauthenticating with another Server or token.
+
+## Rendering and interaction
+
+The table uses cursor loading plus row virtualization. Status card counts cover all Tasks
+matching the applied Task name and advanced filter, ignoring the Status selector.
+Explicit status conditions inside the advanced filter remain effective. Selecting a
+Status changes the highlighted card, Task list and list total without narrowing the
+other cards. List totals include all applied selectors, not just loaded rows.
+Scrolling older rows pauses list polling to avoid reordering
+what the user is reading. Refresh explicitly returns to the top and refreshes data/counts.
+Task selection survives sorting, including browser Back/Forward through sort changes.
+Applying or resetting a saved view also preserves selection when only sorting or
+column layout changes.
+Changing the filter range clears selection, including through browser history.
+Resizing uses per-column widths and a filler for remaining space. JSON paths are read-only
+lookups; missing fields are blank.
+
+The Task name input uses the upstream `name_fuzzy` selector: case-insensitive
+Unicode subsequences, split on whitespace, with every word required and word
+order unrestricted. Empty or whitespace-only searches add no restriction.
+Punctuation is literal; no fzf extended operators or relevance sorting are added.
+Text applies on Enter or blur, respecting IME composition. Exact lookup remains
+available as `name == "..."` in Advanced filter. The URL and saved-view `name`
+field store this input; previously saved name inputs now use fuzzy matching.
+
+The BFF forwards `name_fuzzy` on list, count, and deletion-snapshot requests to
+the Server. It does not filter loaded Tasks in the browser. Status cards ignore
+the Status dropdown but retain name search and advanced filter; list totals use
+all applied selectors. The existing selected-ID deletion UI is unchanged.
+The snapshot endpoint requires at least one effective selector; whitespace-only
+fuzzy input alone is insufficient. The upstream Server must support `name_fuzzy`;
+there is no browser-only matching fallback.
+
+Advanced filter help provides ten built-in examples covering routes, status, priority,
+attempts, errors and custom fields. Route examples use exact-name array membership
+(`"gpu-a100" in routes` and `"gpu-a100" not in routes`); combine checks with
+`or` for any route or `and` for all. Selecting an example applies it immediately
+alongside the status and Task name selectors.
+
+View actions closes when keyboard focus leaves the view controls or moves to the
+Data view picker, so its menu cannot remain open behind that picker. Shift+Tab from
+the first menu item closes the menu and returns focus to the View actions trigger.
+Shared popup positioning clamps to the viewport and chooses above/below placement.
+Escape dismisses a selector from both its trigger and its optional action button,
+returning focus to the trigger. Tab and Shift+Tab move between the trigger and its
+action; Tab from the action leaves and dismisses the menu.
+Selector letter navigation ignores Ctrl, Meta and Alt combinations so browser
+shortcuts keep their normal behavior.
+Keep focus inside menus during internal interactions; Safari can emit a blur with no
+related target before a pointer click completes. Permanent request errors such as invalid
+filters should appear immediately; only transient failures should retry.
+Task action errors and pending indicators belong to the selected Task. Switching Tasks
+resets those indicators without cancelling the previous action; its eventual response
+invalidates the original Task cache, not the newly selected Task. Pending actions remain
+tracked per Task across switching away and back, so returning cannot submit a duplicate.
+Outside interactions dismiss the drawer by synchronously removing its Task from the
+current history entry, allowing a clicked filter or navigation control to update history
+without racing a Back operation. Focus stays with the outside control. The close button
+and Escape retain normal drawer history navigation and restore the originating Task focus.
+
+## Build boundary
+
+Vite produces `frontend/dist`. Hatch includes those assets in the wheel and sdist; the
+installed wheel serves them without Node.js. A successful TypeScript build alone does not
+prove packaging works. See [release verification](../../.agents/sops/releasing.md) for the separate artifact test.
+
+## Batch deletion recovery
+
+Starting, retrying failed Tasks and stopping a batch each disable conflicting actions
+while their request is pending. A failed progress read offers Retry status without
+submitting another deletion, and allows returning to the list with an explicit notice
+that the operation may still run. Stop failures remain visible. Closing the dialog
+stops its polling; it does not cancel an operation already accepted by the backend.
+
+The bounded operation store evicts completed records only. When all slots are active,
+new operations receive a retryable capacity error; running operations remain queryable
+and stoppable until completion.
+
+## Routes and Worker observations
+
+Observation request failures appear as bottom-right notifications, outside the Routes
+layout. Identical messages share one notification listing the affected observations;
+Retry retries all affected active requests. Dismiss (or Escape while focused) keeps
+that message quiet for the current Queue workspace, including refreshes and tab
+switches. Successful requests clear their notification. Unavailable counts and Worker
+observations remain marked in place after dismissal; Refresh remains available.
+Corner notifications share a vertical stack with settings-save failures and transient
+feedback, so recovery controls do not overlap. Notification actions leave the Task
+drawer and its URL open. Modal dialogs remain above the notification stack.
+Each new transient operation message receives a fresh five-second display duration;
+an older timer cannot hide it early. Long column paths wrap within the viewport.
+A notification stays visible while its Retry is pending. Pending retries belong to
+active request identities: changing the Worker filter or tab hides inactive requests
+and cannot disable a new filter's Retry, even when the error text matches. Escape
+from a focused notification dismisses that notification without closing the Task
+drawer; Escape from the drawer still closes the drawer. Worker append failures use
+only the list's Retry loading control, which retries the failed cursor instead of
+refreshing already-loaded pages.
+
+Each Queue has Tasks and Workers tabs and a collapsible Routes sidebar. The sidebar
+combines grouped pending/running Task routes with active Worker routes. Routes with
+only terminal Tasks and no active Workers appear when Include inactive routes is on.
+All group pages must load before absence is treated as zero. Unsupported or failed
+observation requests remain explicit; they never imply that there are zero Workers.
+A route is labeled Inactive only when both Task and Worker observations are available.
+If Task observations fail, a known absence of Workers is labeled No active Workers
+without inferring current Task demand from stale counts.
+Existing Task browsing remains available on Servers without grouped counts.
+
+Selecting a route intersects the Task filter with membership in `routes`, including
+status counts, and filters Workers by `route`. Route and tab navigation use browser
+history; named views include the selected route. Sidebar preferences belong to the
+connection and Queue. Task summary controls use colored numbers followed by status
+words on one line; they retain their status-filter toggle behavior.
+Selecting the current tab or Worker status does not add a duplicate history entry
+when the resulting URL is unchanged.
+
+Worker state counts use grouped observations, independently of the paginated Worker
+list. Observations describe reports, not Task ownership or execution guarantees.
+Normal rows show last seen. Only after more than two 60-second reporting cycles
+without a report does the row show delayed-update and expiry information. Expiry
+uses the Server's `expires_at`; UI polling does not define the reporting interval.
+Delayed-update and expiry messages wrap within their cell so narrow columns do not
+hide the remaining time.
+Failed list refreshes suppress expiry warnings and expose update/retry information.
+Worker IDs, routes and times retain full-value hover tooltips; associated Tasks open
+the existing detail drawer.
+Switching between associated Task links keeps the drawer open. Explicitly closing it
+restores focus to the most recently opened Worker Task link.
+
+Change opens connection settings without discarding the current workspace. Back to
+workspace restores it; a successful connection change clears the query cache.
+Back to workspace is disabled while a connection change is pending. If the change
+fails, returning to the previous workspace becomes available again.
+
+The compact Task summary begins with All, the sum across the five mutually exclusive
+statuses under the applied name, expression and route filters. Selecting All clears
+only the Status selector. Task and Worker summary controls use a quiet rounded
+selection fill. Worker Idle counts are green and Busy counts are blue. Worker status
+selection uses the same styled, keyboard-accessible control as Task filters.
+
+The workspace uses a white surface, medium-weight linked Task names, colored status
+labels and row separators, without nested toolbar/table frames. Route collapse has
+an explicit button and a 140 ms layout transition, disabled for reduced motion.
+Route dots in the sidebar and Task/Worker tables describe current route observations:
+blue for Busy Workers, green for Idle Workers, amber for pending/running Tasks without
+active Workers, gray for inactive routes, and a hollow gray dot when counts are unknown.
+Busy takes precedence over Idle when both are present. A route dot does not describe
+the individual Task's status; each Task keeps its own separate status label.
+
+The Routes divider supports pointer dragging and Left/Right keyboard adjustments.
+Width is stored per connection and Queue, including across collapse and reload.
+The sidebar is bounded to 160–480 px and at most 40% of the viewport. Dragging has
+no layout animation; collapse keeps its short transition. On narrow screens the
+Routes section stacks above content and its horizontal resize handle is hidden.
+
+Task-name search has a 240 px preferred width and expands to its grid cell on narrow
+screens. The Routes toggle stays beside the breadcrumb in both sidebar states. The sidebar
+starts directly with All routes, aligned with the 36 px Task/Worker tab row; there
+is no separate sidebar title or collapse button in the tab row. Selected status
+summaries use a pale version of their status color with matching label text; All uses
+neutral charcoal and a pale gray background. Typography uses 13 px controls, 12 px summary labels and 24 px count numerals.
+
+Queue overview cards use a compact layout capped at 460 px, with the Queue name,
+total Task count, colored status counts, and a thin proportional status distribution
+bar. Status controls retain navigation to the selected status and wrap on narrow
+screens. They have padded hover targets and offset keyboard focus outlines. The
+cards show completed/total Tasks and completion percentage below the bar, and compact
+Worker and Route summaries in the footer. Status numbers use five aligned columns.
+Route counts are distinct routes, classified Busy before Idle before Waiting; Waiting
+means pending/running Task demand without active Workers. Inactive routes are omitted. Worker counts come from paginated Worker
+groups, refreshed every 15 seconds; loading or unavailable observations never display
+as zero. Completion includes succeeded, failed and cancelled Tasks. Failure rate and
+recent Task details are omitted; individual Tasks remain available inside the Queue.

labtasker_webui-0.2.0/docs/releases/v0.2.0.md

@@ -0,0 +1,14 @@
+# v0.2.0
+
+- Add Routes navigation and idle/busy Worker observations, with grouped Queue progress counts. These features require Server 2.2 or later and observation-capable Workers.
+- Add case-insensitive fuzzy Task name search through the Server.
+- Add dismissible warnings when the connected Server is older than the installed Client.
+- Change transient errors to corner notifications with duplicate suppression, dismissal and independent retry recovery.
+- Fix status counts to preserve the applied name and filter when switching Task status.
+- Fix Task drawer navigation, browser history and focus when switching between Tasks or interacting with notifications.
+- Fix keyboard navigation and dismissal for dropdowns and saved-view menus, including WebKit.
+- Fix selection preservation during sorting and saved-view comparison, Worker pagination recovery and long notification wrapping.
+
+Validated against Labtasker 2.2.0 using both Client 2.1.0 and Client 2.2.0. No connection or saved-view migration is required.
+
+Full Changelog: https://github.com/luocfprime/labtasker-webui/compare/v0.1.1...v0.2.0