Skip to content

test(stack): qualify complete slim Docker service graph - #6374

Open
jgoux wants to merge 5 commits into
developfrom
juliengoux/cli-2113-stack-qualify-the-complete-slim-docker-service-graph
Open

test(stack): qualify complete slim Docker service graph#6374
jgoux wants to merge 5 commits into
developfrom
juliengoux/cli-2113-stack-qualify-the-complete-slim-docker-service-graph

Conversation

@jgoux

@jgoux jgoux commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Summary

  • consolidate fragmented Docker coverage into one public 13-service stack journey
  • verify canonical slim images, representative product behavior, and restart persistence
  • prove two automatically allocated sibling stacks keep ports, data, ownership, and cleanup isolated

Context

This is a test-only qualification change for CLI-2113. The existing stack implementation already satisfied the complete Docker graph and sibling-isolation contracts; the new journey makes those release-critical guarantees observable through the public package surface.

@jgoux
jgoux requested a review from a team as a code owner August 28, 2026 10:34
…3-stack-qualify-the-complete-slim-docker-service-graph
@github-actions

github-actions Bot commented Aug 28, 2026

Copy link
Copy Markdown
Contributor

Supabase CLI preview

npx --yes https://pkg.pr.new/supabase/cli/supabase@6755b751660c85cee50ce94f94e447bf4e69ea8f

Preview package for commit 6755b75.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4683e0d172

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread packages/stack/tests/createStack-docker.e2e.test.ts
Comment thread packages/stack/tests/createStack-docker.e2e.test.ts Outdated
@jgoux
jgoux enabled auto-merge August 28, 2026 11:07
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Aug 31, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-08-31T07:07:21.544742Z 6755b75 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6755b75166

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

const remaining = ownedDockerContainers(siblingApiPort).map(
(container) => container.name,
);
expect(remaining).toEqual([]);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Force-remove sibling containers after failed disposal

When sibling.dispose() rejects or its best-effort Docker cleanup leaves a container behind—the failure this assertion is intended to detect—this block only records the assertion error before deleting the data directory and rethrowing. The leaked container remains on the shared daemon, consuming resources and potentially interfering with concurrently running files; after capturing the remaining exact owned names, force-remove those names as a final best-effort cleanup.

AGENTS.md reference: AGENTS.md:L317-L321

Useful? React with 👍 / 👎.

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.

2 participants