Skip to content

fix(sdk): retain bounded final inventory failure diagnostics - #63

Merged
zoeyrose merged 2 commits into
mainfrom
fix/llvm-final-collector-live-repair
Oct 13, 2026
Merged

zoeyrose merged 2 commits into
mainfrom
fix/llvm-final-collector-live-repair

Conversation

@zoeyrose

@zoeyrose zoeyrose commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

Summary

The first hosted collection of the fixed released portable LLVM SDK stopped before filesystem qualification and retained only a generic failure reason. Preserve a bounded validation code and local stage so the next reviewed-main run can identify the failing inventory check.

Implementation / behavior

Track nine fixed inventory stages. Retain an InventoryError code only when both the exception and its single string argument have exact built-in types and the code belongs to the source-defined allowlist. Unknown, hostile or unrelated exceptions remain opaque. Clear the stage after successful inventory collection. Include the diagnostics test in the collector workflow path filter, with a regression that requires every SDK boundary test selected by that workflow to have an explicit path entry.

Keep the fixed SDK 1.22.0 producer, consumer and OCI identities, archive and provider validation, scanner isolation, byte comparisons and owned-container cleanup intact. Failure diagnostics do not establish inventory qualification.

Validation

All 357 isolated native tests passed: 291 tooling and 66 portable tests. Compilation, git diff --check, commit signature and clean worktree checks passed. Independent review reproduced the suites and additional metadata, shader, hostile subclass and post-inventory failure cases with no blocking source findings.

Hosted CI, current-head Codex Code and Security reviews, and automatic Ready reviews are required before merge.

Limitations / follow-up

Hosted collector run 38407172732 failed before the filesystem scan. It retained all 12 LLVM tool identities and successful acquisition cleanup, but its actual inventory failure cause remains unknown. This change adds diagnostics; it does not claim to fix or qualify that SDK. After merge, run one fresh trusted hosted collection and address its actual result. Wrapper adoption remains gated on successful acquisition and filesystem qualification.

Copy link
Copy Markdown
Member Author

@codex review

Please review current commit 1a359c6fd11f04698e7d201e67ff4c9bdf1f35bb, including the exact allowlisted error-code handling, fixed stage diagnostics, success clearing, failure cleanup and unchanged qualification gates.

Copy link
Copy Markdown
Member Author

@codex security review

Please review current commit 1a359c6fd11f04698e7d201e67ff4c9bdf1f35bb, focusing on untrusted inventory/exception data, secret-free diagnostics, exact-type and allowlist checks, and preservation of source, byte, scanner isolation and cleanup gates.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 13, 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-13T18:51:11.666730Z 00ae758 Draft marked ready
🔒 Security Review ✅ Completed 2026-10-13T18:52:25.898813Z 00ae758 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.

@github-actions

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Files

None

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 1a359c6fd1

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@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: 1a359c6fd1

ℹ️ 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 link
Copy Markdown
Member Author

@codex review

Please review corrected current commit 00ae758dda92143ea709d1df89fe7ce5b93a29be. The previous workflow-filter finding is fixed with a failing-before/passing-after regression; all 357 tests, actionlint and independent integrated review pass. Review the complete diagnostics and workflow boundary result.

Copy link
Copy Markdown
Member Author

@codex security review

Please review corrected current commit 00ae758dda92143ea709d1df89fe7ce5b93a29be, including secret-free exact-type/allowlisted diagnostics, the complete SDK test path-filter contract and unchanged trusted hosted acquisition, filesystem scanner and cleanup gates.

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: 00ae758dda

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

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 00ae758dda

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@zoeyrose
zoeyrose marked this pull request as ready for review October 13, 2026 18:48
@zoeyrose
zoeyrose merged commit 96c7fab into main Oct 13, 2026
19 checks passed
@zoeyrose
zoeyrose deleted the fix/llvm-final-collector-live-repair branch October 13, 2026 18:54
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.24.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant