Skip to content

build: trim musl Canvas binary from glibc server image - #237

Merged
lyyzka merged 1 commit into
mainfrom
codex/issue229-glibc-canvas-prune
Oct 20, 2026
Merged

lyyzka merged 1 commit into
mainfrom
codex/issue229-glibc-canvas-prune

Conversation

@lyyzka

@lyyzka lyyzka commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

Remove the unused musl Canvas binary from the Debian/glibc server image while preserving the glibc Canvas binding and formal runtime PDF support. No runtime version, authorization, application behavior or schema changes are introduced.

The original commit fe61654b76c6cc47f70351ad04f2c4819d9111b8 is preserved in integrated PR239 candidate 9a5cfda82ad105d666bf0452df1d615daf6c6a28. Independent native/PDF review passed15checks; exact original CI39419779502 and integrated CI39444057773 succeeded. Final OCI audit verified exactly one removed30,315,608-byte file and18unchanged retained Canvas entries. Compressed image size fell13,021,932bytes (6.3226%).

PR239 completed production acceptance at2026-10-20T15:45:47.705Z:all4services healthy,36native terminal success receipts,16/16acceptance checks, actual Canvas/PDF probes on bothhosts. Detailed evidence.

#229 remains open for controlled cold/warm build and peak-disk evidence; these were not measured by this change. The fixed3.5.3 soak remains untouched.

@lyyzka
lyyzka changed the base branch from integration/215-216-219-final to main October 20, 2026 15:56
@lyyzka
lyyzka marked this pull request as ready for review October 20, 2026 15:56
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 20, 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-10-20T15:59:38.787733Z fe61654 Draft marked ready
ℹ️ 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.

@lyyzka
lyyzka merged commit f3017ce into main Oct 20, 2026
8 checks passed

@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: fe61654b76

ℹ️ 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".

COPY server/package.json server/package-lock.json server/.npmrc ./
COPY package.json /tmp/qualified-package.json
COPY scripts/prune-pdfjs-server-runtime.mjs /tmp/prune-pdfjs-server-runtime.mjs
COPY scripts/prune-glibc-canvas-runtime.mjs /tmp/prune-glibc-canvas-runtime.mjs

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 Track the new pruning script in image CI scope

Add this new Docker build input to the server_source or server_docker paths filter. In the inspected .github/workflows/ci.yml, those filters include only two named root scripts and the Dockerfile/ignore files, so a commit that changes only scripts/prune-glibc-canvas-runtime.mjs produces checks: false and publish: false; the pruning logic can therefore change without validation or rebuilding the server image. This also prevents CI from certifying the exact candidate commit as required.

AGENTS.md reference: AGENTS.md:L10-L10

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