Skip to content

Investigate empty workspace folder in successful MicroSandbox launch result #1514

Closed

Description

@skevetter

A successful Desktop MicroSandbox launch from Devsy v1.24.0-beta.4 ended with an empty remoteWorkspaceFolder, although guest setup used /workspaces/python. The workspace launched successfully; no incorrect mount or download destination was established.

Root cause is confirmed in detached task reporting. Desktop submits workspace up --detach and follows workspace task logs --follow. The log tailer filters the worker's original result envelope; terminal reporting reconstructs it through resultEnvelopeFrom. That mapper copied container/user/warnings/recovery metadata but omitted the folder already stored in Result.SubstitutionContext.

PR #1513 preserves that resolved folder with nil-safe compatibility and corrects generic agent-delivery success wording. Its actual NDJSON response regression fails against the old mapper and passes with the fix, including metadata preservation and nil cases. Local affected race/vet/Windows compilation/Linux lint/scoped hooks passed. All 90 final-head implementation jobs, Greptile 5/5 and the full CodeRabbit review of all three changed files completed without actionable findings. PR #1513 merged as 7754c18; this issue closed automatically.

Action items:

  • Correlate Desktop completion with its detached task reporting path and identify the omitted field.
  • Trace folder resolution and persistence through task success without dumping setup payloads or secrets.
  • Merge the validated repair and confirm the action item closes (PR fix(workspace): preserve detached launch results #1513, merged 2026-10-17).

No user workspace reset, recreation, guest command, provider/default change or configuration mutation was needed. Provider-description PR26 and verified provider release v0.1.11 are separate metadata delivery; this reporting fix requires the Devsy PR.

Activity

  1. skevetter commented on Oct 16, 2026

    @skevetter
    ContributorAuthor

    Read-only follow-up: the exported log does not preserve stdout/stderr identity or command correlation for the empty result field. Current source has other result-envelope producers in lifecycle and exec commands, so the attachment alone does not prove a workspace-up emitter defect. The normal up path retains its substitution-context fallback; guest setup used /workspaces/python. The permitted Desktop log directory contained no companion invocation records.

    The next reproduction should capture command/stream identity for that single result, then compare only the folder at host result receipt and final emission. Do not dump compressed setup payloads or secrets. The later healthy saved workspace result remains later evidence, not proof of the initial response. No workspace reset, recreate, guest command, configuration change, or speculative code patch was performed.

  2. skevetter commented on Oct 16, 2026

    @skevetter
    ContributorAuthor

    Root cause is now confirmed in the detached-task reporting path used by Desktop. Desktop submits workspace up --detach and follows workspace task logs --follow. The tailer filters the worker’s original result envelope, then reports the saved task result through resultEnvelopeFrom. That mapper copies the container ID, user, warnings and recovery status but omits the stored SubstitutionContext.ContainerWorkspaceFolder.

    The guest setup and normal foreground-up emitter preserve the folder. This is a missing field in the detached completion response, not an incorrect mount or download destination. A nil-safe fix and a regression for the actual single-NDJSON success response are being validated in #1513, retaining existing metadata and nil-result compatibility. No user workspace restart, recreation, provider/default change or configuration mutation was needed.

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