Skip to content

Fix task control and resource monitoring for 0.40.1 - #20

Merged
LingzheZhao merged 3 commits into
mainfrom
codex/task-control-ownership
Sep 28, 2026
Merged

LingzheZhao merged 3 commits into
mainfrom
codex/task-control-ownership

Conversation

@LingzheZhao

@LingzheZhao LingzheZhao commented Sep 28, 2026 •

Copy link
Copy Markdown
Member

Basic authorization allowed users to control other users’ notebooks, shells, commands, TensorBoards, experiments, and queued jobs. Enforce owner/admin checks across individual and bulk operations, preflight job-queue batches before any mutation, and hide unavailable controls in the WebUI.

Restore allocation/container/runtime/GPU metric mappings when the master recovers running tasks. Registration and teardown remain balanced across duplicate events and multiple resources, so resource charts keep updating after a master restart.

Expose task measurements through /api/v1/tasks/{task_id}/resources, with typed samples, generated Python/TypeScript clients, and the bundled REST reference. Preserve the existing WebUI API, fix internal documentation links, and prepare concise 0.40.1 notes and stable-release publishing.

Validation: targeted backend tests with PostgreSQL 14 and Go race detection; focused WebUI permission/action tests and TypeScript checks; actionlint. The Actions-built candidate passed real HTTP ownership/bulk-control checks, metrics and documentation checks, and a running CPU task across image replacement and another master restart. The task kept its container and start time, metric mappings recovered exactly once, and termination cleared them without negative counts.

@LingzheZhao LingzheZhao changed the title Fix task ownership controls and expose resource metrics API Fix task control and resource monitoring for 0.40.1 Sep 28, 2026
@LingzheZhao
LingzheZhao merged commit 8e26a69 into main Sep 28, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant