Desktop: jobs — submit, follow, stop #81

Closed
opened 2026-10-07 18:00:06 +00:00 by rvnminers-A-and-N · 3 comments
Owner

The daemon side is built and described in docs/desktop-backend.md. Build against the integration branch, with examples/desktop-backend.sh for a backend to run.

  • Submit a job (SubmitJob): workload, parameters, tasks, memory and graphics-card requirements, private
  • Live list (WatchJobs) and one job's progress and log (WatchJobEvents)
  • Stop a job (CancelJob)

Daemon side: #62, #63, #65.

The daemon side is built and described in [`docs/desktop-backend.md`](../blob/integration/docs/desktop-backend.md). Build against the `integration` branch, with `examples/desktop-backend.sh` for a backend to run. - [ ] Submit a job (`SubmitJob`): workload, parameters, tasks, memory and graphics-card requirements, private - [ ] Live list (`WatchJobs`) and one job's progress and log (`WatchJobEvents`) - [ ] Stop a job (`CancelJob`) Daemon side: #62, #63, #65.
Owner

Implemented in the desktop Operations view on branch feat/desktop-issues: submit distributed/full-worker jobs with task, memory, GPU and private options; live WatchJobs/WatchJobEvents updates; cancel; and fetch output blobs. Verified against the local three-node demo.

Implemented in the desktop Operations view on branch `feat/desktop-issues`: submit distributed/full-worker jobs with task, memory, GPU and private options; live WatchJobs/WatchJobEvents updates; cancel; and fetch output blobs. Verified against the local three-node demo.
Owner

Local implementation update (not yet submitted or merged):

The Operations jobs tab wires SubmitJob (workload, JSON parameters, mode, task count, memory/GPU requirements and private flag), WatchJobs, WatchJobEvents and CancelJob. It renders job state/progress and a bounded recent event list; operation labels have translations.

Remaining acceptance work: submit and complete an actual workload, inspect streamed progress/events, cancel a running job, verify failure/disconnect/reconnect behavior and ensure stream cleanup. Stream errors currently have silent handlers, so recovery/error feedback needs explicit checking rather than marking this done.

Shared layout and connection-state behavior is tracked in #99. Keep this open until verified and reviewed/merged.

Local implementation update (not yet submitted or merged): The Operations jobs tab wires SubmitJob (workload, JSON parameters, mode, task count, memory/GPU requirements and private flag), WatchJobs, WatchJobEvents and CancelJob. It renders job state/progress and a bounded recent event list; operation labels have translations. Remaining acceptance work: submit and complete an actual workload, inspect streamed progress/events, cancel a running job, verify failure/disconnect/reconnect behavior and ensure stream cleanup. Stream errors currently have silent handlers, so recovery/error feedback needs explicit checking rather than marking this done. Shared layout and connection-state behavior is tracked in #99. Keep this open until verified and reviewed/merged.
Author
Owner

Merged in the desktop stack (#101 to #110, with #116). What the review found still to do is in #117.

Merged in the desktop stack (#101 to #110, with #116). What the review found still to do is in #117.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Sisyphus/Sisyphus#81