Skip to content

scope worker image rebuild inputs - #223

Merged
pmbstyle merged 1 commit into
mainfrom
feature/worker-image-fingerprint-scope
Aug 13, 2026
Merged

scope worker image rebuild inputs#223
pmbstyle merged 1 commit into
mainfrom
feature/worker-image-fingerprint-scope

Conversation

@pmbstyle

Copy link
Copy Markdown
Owner

Summary

  • derive the worker-image fingerprint from the local import closure rooted at the worker entrypoint
  • keep the Dockerfile, dependency metadata, lockfile, and worker prompt as explicit inputs
  • fail closed to all Python source when the runtime import surface cannot be resolved or uses dynamic loading
  • stop README and main-process-only routing, memory, Telegram, and prompt changes from invalidating the worker image

Container impact

  • install locked dependencies without installing the project package
  • continue loading project source through the existing /app/src runtime path
  • remove README from the Docker build context contract

Validation

  • 54 focused worker, image-contract, isolation, and restart tests
  • full Python test suite (one expected Windows-only skip)
  • Ruff, Black, MyPy, and diff checks
  • Dockerfile build check
  • disposable worker image build and import smoke completed during local validation

@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@pmbstyle, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 19 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 051a86e7-7d0b-4aac-871f-784de54575e4

📥 Commits

Reviewing files that changed from the base of the PR and between 2e0ac6d and 93849d1.

📒 Files selected for processing (4)
  • docker/Dockerfile
  • src/octopal/runtime/workers/launcher_factory.py
  • tests/test_worker_image_contract.py
  • tests/test_worker_launcher_factory.py

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.

@pmbstyle
pmbstyle merged commit 4b1f36d into main Aug 13, 2026
7 checks passed
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