Skip to content

Post-2026.1.0.52 sweep, Tier 2: driver-command-queue API, sandbox owner by display name - #25

Closed
nahumtimerman wants to merge 1 commit into
docs/2026.1-patch-sweep-tier1from
docs/2026.1-patch-sweep-tier2
Closed

Post-2026.1.0.52 sweep, Tier 2: driver-command-queue API, sandbox owner by display name#25
nahumtimerman wants to merge 1 commit into
docs/2026.1-patch-sweep-tier1from
docs/2026.1-patch-sweep-tier2

Conversation

@nahumtimerman

Copy link
Copy Markdown
Collaborator

Second batch of the post-2026.1.0.52 catch-up. Based on docs/2026.1-patch-sweep-tier1 (#24) — both tiers edit whats-new.md, so they're stacked to avoid a conflict. Merge #24 first and this will retarget to main.

Driver command queue inspection and recovery API

Trunk CS 189900 (ticket 67008). New how-to page for the four sysadmin-gated methods:

Scope Inspect Cancel
One reservation GetRunningCommands CancelResourceCommand (one, by id)
One resource, all reservations GetResourceCommandExecutions ClearResourceCommands (all)

Signatures, parameter semantics and the sysadmin requirement come from Tools/API/XmlDocumentation/TestShell API/ApiDocumentation.xml, where all four are registered Lang="all". The response shape is RunningCommandListInfo from ApiCommandResult.cs — a Commands list of RunningCommandInfo with ExecutionId, ResourceFullName, CommandName, Status, StartTime, ReservationId.

The page leads with why the resource-scoped pair exists, since that's the part the method names don't convey: a command belonging to a previous — possibly already ended — sandbox blocks an exclusive, non-concurrent resource, and a new sandbox can't see it because everything it can reach is reservation-scoped. It also notes that ClearResourceCommands cancels out-of-band and so doesn't wait behind the very command it's clearing, which is what makes it usable from a Setup script.

Carries a warning that cancelling a driver command mid-run leaves the device in whatever state it reached — recovery tool, not routine flow.

Sandbox owners and permitted users accepted by display name

CS 189998 + 190000 (ticket 67309), with the release note at Docs/ReleaseNotes/2026.1/sandbox-owner-resolved-by-display-name.md. Keeps the two points that make it safe to rely on: usernames are matched first so no existing behavior changes, and a display name shared by several users is rejected rather than resolved arbitrarily.

Files

  • docs/devguide/available-cs-api/useful-cs-api-examples/inspect-and-clear-driver-commands.md — new page (sidebar_position: 10; the category index is an auto-generated DocCardList, so no index edit needed)
  • docs/release-notes/whats-new.md — two new 2026.1 entries

npx docusaurus build passes; the 3 broken links reported are pre-existing and unrelated.

🤖 Generated with Claude Code

… by display name

Driver command queue inspection and recovery (Trunk CS 189900, ticket 67008).
New how-to page for the four sysadmin-gated methods - GetRunningCommands,
GetResourceCommandExecutions, CancelResourceCommand, ClearResourceCommands -
plus a What's New entry.

Signatures, parameter semantics and the sysadmin requirement come from
Tools/API/XmlDocumentation/TestShell API/ApiDocumentation.xml, where all four
are registered Lang="all". The response shape is RunningCommandListInfo from
ApiCommandResult.cs: a Commands list of RunningCommandInfo with ExecutionId,
ResourceFullName, CommandName, Status, StartTime and ReservationId. The page
leads with why the resource-scoped pair exists - a command belonging to a
previous, possibly ended, sandbox blocking an exclusive non-concurrent
resource, which a new sandbox cannot see because its view is reservation
scoped - and notes that ClearResourceCommands cancels out-of-band so it does
not wait behind the command it is clearing, which is what makes it usable
from Setup.

Sandbox owners and permitted users accepted by display name (CS 189998 +
190000, ticket 67309; release note Docs/ReleaseNotes/2026.1/
sandbox-owner-resolved-by-display-name.md). Keeps the two points that make it
safe to rely on: usernames are matched first so nothing existing changes, and
an ambiguous display name is rejected rather than resolved arbitrarily.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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