Skip to content

chore: sync public mirror from internal - #1371

Merged
evalops-mirror[bot] merged 1 commit into
mainfrom
sync/public-release-mirror
Oct 8, 2026
Merged

evalops-mirror[bot] merged 1 commit into
mainfrom
sync/public-release-mirror

Conversation

@evalops-mirror

@evalops-mirror evalops-mirror Bot commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • sync the sanitized public tree from dx-corp/mono
  • keep dx-corp/code as a generated public mirror of the private source of truth
  • preserve public-owned CI and trusted-publishing workflows from the public checkout
  • internal source SHA: 871bfe3ec25bd3506fe2725b8a893bb372a30928
  • last generated public sync base: ab0c9ce0cfe05d6ac5519333466b87b03fa11a0c
  • previewed public-tree drift: 2 file(s) to copy/update and 0 stale file(s) to delete
  • public-only commits since last generated sync: 0
  • to pause generated syncs while hand-editing this branch, apply the sync-hold label to this PR; the sync workflow skips every push while it is set

Source-of-truth status

Projection: deixic-code

  • Source: dx-corp/mono@871bfe3ec25bd3506fe2725b8a893bb372a30928

  • Prior destination base: ab0c9ce

  • Content SHA-256: 880c2ccbeadddda04e3edcfcd39e25a881ef94e89baca25c58c3d4af9b9a66bb

  • Result: drift_detected; 2 changed, 0 deleted

  • Destination-owned content is preserved. Destination CI is a separate health signal.

  • copy/update .github/actions/setup-sccache/configure.sh

  • copy/update .repository-projection.json

Drift sample

  • copy/update .github/actions/setup-sccache/configure.sh
  • copy/update .repository-projection.json

Public-only commits since last generated sync

  • none detected since last generated sync

Validation

  • generated by the sync-public-release-mirror workflow in public-tree mode

Test Plan

  • generated by the maestro-sync-public-release-mirror workflow in public-tree mode
  • public-source-provenance require-internal-pr confirms internal source PR lineage
  • generated mirror PRs use the slim public CI path (fmt/clippy/smoke + provenance); full cargo test/evals already ran on internal main for this SHA
  • bot review threads on generated mirror PRs are advisory and do not block the next sync update

Staged Rollout

  • Staging is unnecessary for this generated mirror PR: it does not independently promote user-visible behavior. It mirrors already-reviewed internal source from dx-corp/mono@871bfe3ec25bd3506fe2725b8a893bb372a30928, including existing hidden/evaluation surfaces, and keeps public package parity behind the established public-source-provenance gate.

@evalops-mirror
evalops-mirror Bot requested review from a team as code owners October 8, 2026 14:34
@evalops-mirror

evalops-mirror Bot commented Oct 8, 2026

Copy link
Copy Markdown
Contributor Author

Resolved 0 review-bot thread(s) on this generated public mirror PR.
Left 0 human-started thread(s) unresolved.

Review of mirrored code belongs on the mono source PR.
See https://github.com/dx-corp/mono/issues/9100 for the triage pattern.

@evalops-mirror
evalops-mirror Bot enabled auto-merge (squash) October 8, 2026 14:35
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 8, 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-08T14:39:15.559518Z 4915be6 PR opened
ℹ️ 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.

@evalops-mirror
evalops-mirror Bot merged commit 385686a into main Oct 8, 2026
10 checks passed
@evalops-mirror
evalops-mirror Bot deleted the sync/public-release-mirror branch October 8, 2026 14:37

@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: 4915be67cd

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +323 to +326
# The startup client can time out just before its job-local daemon becomes
# ready. The existing statistics request must still succeed and prove the
# selected backend; a timeout alone never admits an unavailable cache.
echo "::warning::sccache startup client timed out; checking daemon readiness"

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Require a daemon connection before accepting the timeout

When --start-server times out because backend initialization never completes, this branch continues on the assumption that --show-stats proves daemon readiness. However, the sccache v0.17.0 used by setup-rust explicitly synthesizes mostly empty statistics when it cannot connect to a server and exits successfully; it also derives the reported cache location from the configuration, so the checks below can pass with no daemon running (sccache v0.17.0 source). The setup action then succeeds, but subsequent compiler invocations can repeatedly attempt and fail to start the missing daemon. Use a probe that fails unless it connects to the job's UDS, or retry until that socket accepts a connection before suppressing the startup error.

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.

0 participants