Skip to content

docs: align ProviderSandbox parameter docstrings with current signatures #124

Closed

Description

@anycodes

Public 0.4.0a3 ProviderSandbox.create/connect/list/kill_by_id docstrings still document retired api_key/api_url/domain arguments and alias agreement behavior, although the real signatures accept only sandbox_api_key/sandbox_base_url/sandbox_domain where applicable. Their four generated synchronous wrappers copy the same stale documentation. kill_by_id additionally lists sandbox_domain even though its control-plane signature does not accept it. get_info_by_id/set_timeout_by_id refer to kill_by_id for overrides.

Expected: document only real canonical ProviderSandbox parameters; preserve all signatures, runtime behavior and standard Sandbox/AsyncSandbox ApiParams. No compatibility aliases. Update the lockstep client/server pair to the next alpha 0.4.0a4 for immutable package delivery after normal review/CI. Keep current install recommendations on genuinely published a3 until a4 succeeds.

Acceptance: direct and generated sync doc/signature correspondence, actual retired-keyword rejection without network calls, owner checks and 13 exact-head CI checks, independent review and normal merge, immutable release with four artifact/public hash matches and fresh official installation. Historical a3 evidence remains unchanged. No new cloud/PTY/catalog claim.

Activity

  1. anycodes commented on Oct 25, 2026

    @anycodes
    ContributorAuthor

    Delivered by merged PR #125, source 100da4661809f91a5d50e2722d1f4a8d4da3b131, after independent review and all 13 exact-head checks. The four ProviderSandbox docstrings and their sync copies match unchanged real signatures; standard ApiParams remains unchanged.

    Immutable v0.4.0a4 and publication run 40215483508 completed SUCCESS on attempt 2. Attempt 1 is retained as a real metadata-404 failure: six probes over 50 seconds, before fresh installation. Both preserved artifact sets have identical four-file hashes matching official metadata and downloaded bytes; recovery skipped all four existing files.

    Independent fresh official client-a4 installation automatically installed server-a4; pip check, standard/provider/server imports, all 12 lifecycle docstrings, 24 actual retired-keyword rejections and exact reviewed API source bytes passed. Actual public-package local HTTP health/shell/file behavior and owned process cleanup passed. No new cloud/model/catalog certification is inferred. Current installation/navigation synchronization and finite propagation-window follow-up are separate source-only delivery work; previous a3 evidence is unchanged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions