Skip to content

fix(e2e): stop asserting current_task on public workspace GET - #984

Merged
HongmingWang-Rabbit merged 1 commit into
stagingfrom
fix/e2e-current-task-public-get
Apr 19, 2026
Merged

HongmingWang-Rabbit merged 1 commit into
stagingfrom
fix/e2e-current-task-public-get

Conversation

@HongmingWang-Rabbit

Copy link
Copy Markdown
Contributor

Summary

PR #966 stripped `current_task`, `last_sample_error`, and `workspace_dir` from the public `GET /workspaces/:id` response (security fix — those fields leak task bodies / agent errors / host paths to any workspace-bearer holder). The E2E smoke test kept asserting `"current_task":"Analyzing document"` on the single-workspace GET, so every post-#966 CI run has failed with `60 passed, 2 failed`.

Swap the per-workspace asserts to `active_tasks` (still exposed, canonical busy signal) and keep the list-endpoint check that proves admin-auth'd callers still see `current_task` end-to-end.

Blocks

Staging → main promotion (#983 — this test drift is the only red on the promotion PR).

🤖 Generated with Claude Code

PR #966 intentionally stripped current_task, last_sample_error, and
workspace_dir from the public GET /workspaces/:id response to avoid
leaking task bodies to anyone with a workspace bearer. The E2E smoke
test hadn't caught up — it was still asserting "current_task":"..."
on the single-workspace GET, which made every post-#966 CI run fail
with '60 passed, 2 failed'.

Swap the per-workspace asserts to check active_tasks (still exposed,
canonical busy signal) and keep the list-endpoint check that proves
admin-auth'd callers still see current_task end-to-end.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@HongmingWang-Rabbit
HongmingWang-Rabbit merged commit dcc4ec0 into staging Apr 19, 2026
9 checks passed
molecule-ai Bot pushed a commit that referenced this pull request Apr 21, 2026
fix(e2e): stop asserting current_task on public workspace GET
@HongmingWang-Rabbit
HongmingWang-Rabbit deleted the fix/e2e-current-task-public-get branch April 24, 2026 00:11
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