Skip to content

Feat/223 harbor compatibility - #232

Merged
Perry2004 merged 2 commits into
mainfrom
feat/223-harbor-compatibility
Jun 22, 2026
Merged

Feat/223 harbor compatibility#232
Perry2004 merged 2 commits into
mainfrom
feat/223-harbor-compatibility

Conversation

@Perry2004

Copy link
Copy Markdown
Collaborator

No description provided.

@Perry2004
Perry2004 merged commit 924ed59 into main Jun 22, 2026
8 checks passed
@Perry2004
Perry2004 deleted the feat/223-harbor-compatibility branch June 22, 2026 22:59
@github-project-automation github-project-automation Bot moved this from Todo to Done in ClawBench Jun 22, 2026
reacher-z added a commit that referenced this pull request Jun 27, 2026
Resolve conflicts after main reverted harbor-as-a-harness (#229) and added
the separate harbor adaptor (#232), plus the remote-browser CDP refactor (#235).

Resolution:
- pyproject.toml: keep all harbor entry points — main's clawbench-harbor-adapt
  alongside the feature's clawbench-export-harbor / clawbench-harbor-parity.
- runtime/harnesses/harbor/{harbor_driver.py,run-harbor.sh}: restore (main
  deleted, branch modified) to preserve the harbor harness the feature drives;
  re-add the harbor block to harnesses.yaml and "harbor" to EXPECTED_HARNESSES.
- Restore Dockerfile.harbor / setup-harbor.sh / usage-emitter.py (deleted by
  main) so the registered harbor harness stays complete.
- Adapt harbor to main's shared CDP API: read CLAWBENCH_BROWSER_CDP_URL instead
  of the hard-coded http://127.0.0.1:9222 (harbor_driver.py CDP_URL + docstring,
  run-harbor.sh readiness probe) to satisfy test_harnesses_use_shared_browser_cdp_env.
- Adopt main's evolution everywhere else (runtime-server rename, browser_runtime
  providers, eval/harbor_adapter, runtime/harbor, base entrypoint) unchanged.

ruff check + format, pyright (0 errors), and pytest (161 passed) all green.
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