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

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

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: labtasker-webui
-Version: 0.2.0
+Version: 0.4.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
@@ -29,19 +29,23 @@ 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 applied Task name and advanced filter, across all statuses; the Status selector narrows only the Task list and its total.
+  cancelled Tasks. Running Tasks can show a compact circular completion indicator
+  from their latest reported progress. 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.
+  reviewing historical work. Resize Worker columns or double-click them to fit loaded
+  content. 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.
 - **Reusable data views:** Save filters, sorting, and column layouts for each
   connection and Queue. Switch views without rebuilding the table each time.
 - **Complete Task inspection:** Open a Task to inspect its arguments, metadata,
-  execution timeline, errors, and results. Cancel, requeue, or delete selected
-  Tasks through explicit controls.
+  execution timeline, errors, and results. Cancel, requeue, delete, or set the priority
+  of selected Tasks through explicit controls.
 - **Easy local use:** Launch from Python without Node.js. Remember connections
   and UI preferences in the WebUI working directory's `.labtasker/` folder.
 
@@ -104,7 +108,26 @@ The list loads more Tasks as you scroll and preserves existing selections.
 While reading older rows, background refresh does not reorder the list.
 Returning to the top resumes live refresh; **Refresh** updates it explicitly.
 Click a Task to open its details. Dates use local time, with full timestamps
-available on hover.
+available on hover. When a Task has reported progress, its retained progress JSON,
+report attempt, and update time appear before the final Result section.
+
+Workers may opt into the circular indicator by reporting finite numeric
+`completed` and `total` values:
+
+```python
+labtasker.report_progress(
+    {
+        "completed": completed_cases,
+        "total": total_cases,
+        "metrics": {"validation_loss": validation_loss},
+    }
+)
+```
+
+These names are a display convention, not a Server schema. Other progress keys
+remain user-defined. A running Task without a valid `completed / total` ratio
+shows `—`; non-running rows leave the Progress column blank. The Progress column
+starts compact and can be resized like the other data columns.
 
 ## Project profiles
 
@@ -153,13 +176,13 @@ responses.
 ## Scope
 
 Labtasker WebUI inspects existing workloads and supports cancellation, requeue,
-and permanent deletion of explicitly selected Task IDs. Batch deletion reports
-each result; it is not an atomic operation.
+priority updates, and permanent deletion of explicitly selected Task IDs. Batch
+operations report partial failures; deletion is not an atomic operation.
 
-Use the Labtasker Client, CLI, or Workers to submit and execute Tasks. The WebUI
-does not submit or edit Tasks, schedule work, allocate resources, or manage the
-Labtasker process. Local mode only attaches to an existing instance and never
-opens its database.
+Use the Labtasker Client, CLI, or Workers to submit and execute Tasks. Apart from
+setting priority for an explicit selection, the WebUI does not submit or edit Tasks,
+schedule work, allocate resources, or manage the Labtasker process. Local mode only
+attaches to an existing instance and never opens its database.
 
 ## Documentation
 
@@ -185,13 +208,3 @@ 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 → labtasker_webui-0.4.0}/README.md

@@ -10,19 +10,23 @@ 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 applied Task name and advanced filter, across all statuses; the Status selector narrows only the Task list and its total.
+  cancelled Tasks. Running Tasks can show a compact circular completion indicator
+  from their latest reported progress. 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.
+  reviewing historical work. Resize Worker columns or double-click them to fit loaded
+  content. 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.
 - **Reusable data views:** Save filters, sorting, and column layouts for each
   connection and Queue. Switch views without rebuilding the table each time.
 - **Complete Task inspection:** Open a Task to inspect its arguments, metadata,
-  execution timeline, errors, and results. Cancel, requeue, or delete selected
-  Tasks through explicit controls.
+  execution timeline, errors, and results. Cancel, requeue, delete, or set the priority
+  of selected Tasks through explicit controls.
 - **Easy local use:** Launch from Python without Node.js. Remember connections
   and UI preferences in the WebUI working directory's `.labtasker/` folder.
 
@@ -85,7 +89,26 @@ The list loads more Tasks as you scroll and preserves existing selections.
 While reading older rows, background refresh does not reorder the list.
 Returning to the top resumes live refresh; **Refresh** updates it explicitly.
 Click a Task to open its details. Dates use local time, with full timestamps
-available on hover.
+available on hover. When a Task has reported progress, its retained progress JSON,
+report attempt, and update time appear before the final Result section.
+
+Workers may opt into the circular indicator by reporting finite numeric
+`completed` and `total` values:
+
+```python
+labtasker.report_progress(
+    {
+        "completed": completed_cases,
+        "total": total_cases,
+        "metrics": {"validation_loss": validation_loss},
+    }
+)
+```
+
+These names are a display convention, not a Server schema. Other progress keys
+remain user-defined. A running Task without a valid `completed / total` ratio
+shows `—`; non-running rows leave the Progress column blank. The Progress column
+starts compact and can be resized like the other data columns.
 
 ## Project profiles
 
@@ -134,13 +157,13 @@ responses.
 ## Scope
 
 Labtasker WebUI inspects existing workloads and supports cancellation, requeue,
-and permanent deletion of explicitly selected Task IDs. Batch deletion reports
-each result; it is not an atomic operation.
+priority updates, and permanent deletion of explicitly selected Task IDs. Batch
+operations report partial failures; deletion is not an atomic operation.
 
-Use the Labtasker Client, CLI, or Workers to submit and execute Tasks. The WebUI
-does not submit or edit Tasks, schedule work, allocate resources, or manage the
-Labtasker process. Local mode only attaches to an existing instance and never
-opens its database.
+Use the Labtasker Client, CLI, or Workers to submit and execute Tasks. Apart from
+setting priority for an explicit selection, the WebUI does not submit or edit Tasks,
+schedule work, allocate resources, or manage the Labtasker process. Local mode only
+attaches to an existing instance and never opens its database.
 
 ## Documentation
 
@@ -166,13 +189,3 @@ 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 → labtasker_webui-0.4.0}/docs/reference/specification.md

@@ -7,8 +7,9 @@ Browser (React, Query, Table)
 ```
 
 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
+operation snapshots. The UI observes Tasks and supports cancel, requeue, selected-ID
+deletion and selected-ID priority updates; it does not submit Tasks or edit other Task
+fields. Local attachment discovers and uses the existing
 socket without managing the Labtasker process or opening its database.
 
 ## Server version warnings
@@ -44,7 +45,7 @@ Neither credentials nor version observations are written to the profile.
 | 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 |
+| Current Task column layout and Worker column widths | 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 |
@@ -83,9 +84,51 @@ Task selection survives sorting, including browser Back/Forward through sort cha
 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.
+The selection column remains pinned while the Task table scrolls horizontally.
+An explicit Task selection exposes Cancel Tasks, Requeue Tasks, Delete Tasks and Set
+priority actions. Clear selection only removes the current checkmarks. Each lifecycle
+action is enabled only when every selected Task has a compatible status, using the same
+rules as the Task drawer: Cancel accepts pending/running, Requeue accepts
+pending/failed/cancelled, while Delete and priority updates reject running. Priority
+accepts any JavaScript-safe integer, including zero and negative values. Disabled actions
+explain the required and incompatible statuses on hover or keyboard focus. Batch Cancel,
+Requeue and priority updates retain failed Task IDs for retry while clearing successful
+IDs from the selection.
 Resizing uses per-column widths and a filler for remaining space. JSON paths are read-only
 lookups; missing fields are blank.
 
+Default Task column widths are Status 117 px, Progress 88 px, Attempt 83 px,
+Priority 79 px, Created and Updated 103 px, and Duration 86 px. Saved widths
+continue to override these defaults within their connection and Queue scope.
+Progress can be resized down to 56 px, and this minimum width survives reload.
+
+The built-in Progress column is 88 px wide by default and centered. It retains
+the table's column-resizing behavior. Non-running Task rows leave it blank. A
+running Task shows a 14 px circular progress indicator only
+when its `progress` object contains finite numeric `completed` and `total`
+values with `0 <= completed <= total` and `total > 0`. The accessible value and
+popover show the floor of `completed / total * 100`, correcting floating-point
+roundoff at integer boundaries (29 of 100 shows 29%). Incomplete progress never
+shows 100%. The compact ring has no
+center text, follows the primary UI color and transitions over 250 ms. Other
+running Tasks show `—`, including Tasks without progress, incomplete display fields
+and values above the declared total. The column is not sortable. It follows the
+existing Task-list polling and pause rules rather than creating another refresh
+loop. The Status column has a 104 px minimum so every status badge remains fully
+visible, including when an older saved layout requested a narrower width.
+
+Hovering or focusing the ring opens a viewport-contained summary with the exact
+completed and total values, progress attempt, Server report time and a generic
+JSON preview. Clicking pins the same summary until an outside interaction or
+Escape. Clicking inside the summary does not open the Task drawer. Escape works
+from the summary's contents and returns focus to the ring. Task row keyboard
+navigation only handles keys on the row itself; Space on its checkbox toggles
+selection without opening details. The UI assigns no meaning to other progress keys. Task details show a
+Progress JSON section immediately before Result whenever progress is non-null,
+including for terminal Tasks whose last snapshot was retained. Its heading
+shows the Server-owned attempt and report time. Null progress adds no details
+section.
+
 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.
@@ -198,6 +241,10 @@ Worker IDs, routes and times retain full-value hover tooltips; associated Tasks
 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.
+Worker, Status, Route, Task and Last seen columns have independent resize handles. Their
+default widths are 240, 100, 200, 240 and 210 px respectively. Pointer dragging and
+Left/Right keyboard adjustment change only the chosen column; double-click fits that
+column to loaded content. Widths persist per connection and Queue.
 
 Change opens connection settings without discarding the current workspace. Back to
 workspace restores it; a successful connection change clears the query cache.

labtasker_webui-0.4.0/docs/releases/v0.2.1.md

@@ -0,0 +1,6 @@
+# v0.2.1
+
+- Add status-aware Cancel, Requeue and Delete actions for selected Tasks, with disabled-state guidance and partial-failure recovery.
+- Fix Task selection controls so checkboxes remain visible while horizontally scrolling wide tables.
+
+Full Changelog: https://github.com/luocfprime/labtasker-webui/compare/v0.2.0...v0.2.1

labtasker_webui-0.4.0/docs/releases/v0.4.0.md

@@ -0,0 +1,17 @@
+# v0.4.0
+
+- Add compact Task progress indicators with exact, keyboard-accessible progress
+  details and retained Progress JSON in the Task drawer.
+- Add priority updates for explicitly selected Tasks, including negative and zero
+  priorities, status guidance and partial-failure recovery.
+- Add resizable Worker columns with pointer, keyboard and double-click fit interactions,
+  persisted per connection and Queue.
+- Change selected-Task action labels so cancelling Tasks and clearing the current
+  selection are unambiguous.
+- Fix Task table defaults and interactions for compact Progress, status visibility and
+  horizontal scrolling.
+
+Priority updates use the Labtasker v2 Task update endpoint and remain unavailable for
+running Tasks. Existing profiles and saved views require no migration.
+
+Full Changelog: https://github.com/luocfprime/labtasker-webui/compare/v0.2.1...v0.4.0