Skip to content

fix: make recovery readiness checks reach Unity connection errors#1829

Merged
hatayama merged 2 commits into
fix/macos-e2e-integrationfrom
fix/smoke-runner-pin
Jul 18, 2026
Merged

fix: make recovery readiness checks reach Unity connection errors#1829
hatayama merged 2 commits into
fix/macos-e2e-integrationfrom
fix/smoke-runner-pin

Conversation

@hatayama

@hatayama hatayama commented Jul 18, 2026

Copy link
Copy Markdown
Owner

Summary

  • Recovery/readiness smoke checks now exercise the intended Unity connection failure path for temporary projects.
  • The self-test fixture supplies the runner pin required by the dispatcher.

User Impact

  • Stale recovery-state validation no longer fails early with a project-resolution error.

Changes

  • Copy the source project's .uloop/project-runner-pin.json into the temporary Unity project before running the stale-state check.
  • Keep the fake project fixture aligned with the required project metadata.

Verification

  • sh scripts/test-smoke-cli-recovery-readiness.sh
  • go run scripts/smoke-cli-recovery-readiness.go --project-path /Users/a12115/ghq/hatayama/unity-cli-loop --uloop-path dist/darwin-arm64/uloop --timeout 120 --launch-timeout 240

Refs: Mac POSIX E2E recovery/readiness fix specification, To-Dos 2-4.

Review in cubic

Copy the source project's runner pin into the temporary Unity project so the dispatcher reaches the intended unreachable-server assertion. Keep the fake harness fixture aligned with the smoke test's required project metadata.
@coderabbitai

coderabbitai Bot commented Jul 18, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 610d0426-5d9a-4433-b09c-3c02fc3c1eb8

📥 Commits

Reviewing files that changed from the base of the PR and between 5f5566f and b8ea9b2.

📒 Files selected for processing (1)
  • scripts/smoke-cli-recovery-readiness.go
🚧 Files skipped from review as they are similar to previous changes (1)
  • scripts/smoke-cli-recovery-readiness.go

📝 Walkthrough

Walkthrough

The smoke-test harness prepares runner-pin metadata, passes the source project path into stale-recovery testing, and copies the pin into the temporary Unity project before writing stale server state.

Changes

Recovery pin setup

Layer / File(s) Summary
Smoke harness pin preparation
scripts/test-smoke-cli-recovery-readiness.sh
Creates the temporary project’s .uloop directory and copies project-runner-pin.json into it.
Temporary project pin propagation
scripts/smoke-cli-recovery-readiness.go
Passes the source project path through stale recovery, copies the runner pin into the temporary project, and stops on copy errors before writing stale state.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly reflects the main change: recovery readiness checks now reach the Unity connection error path.
Description check ✅ Passed The description matches the changeset and explains the recovery/readiness smoke-test fix and verification steps.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/smoke-runner-pin

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Explain why the temporary project must receive the runner pin before the stale recovery assertion runs, so the dispatcher reaches the intended connection failure path.
@hatayama
hatayama merged commit 7ae6771 into fix/macos-e2e-integration Jul 18, 2026
2 checks passed
@hatayama
hatayama deleted the fix/smoke-runner-pin branch July 18, 2026 05:58
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