Skip to content

v1.3.0

Choose a tag to compare

View all tags
@ZhenghuaBao ZhenghuaBao released this 22 Jul 07:49
· 50 commits to main since this release
v1.3.0
0c082f9
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Orca-Code-Review v1.3.0

Backward-compatible minor: adds a wall-clock guard on the review engine.

New

  • timeout-minutes input (default 20). Wraps ocr review in GNU timeout --kill-after=10s: SIGTERM at N minutes, SIGKILL 10s later if the engine ignored the term. On timeout, the check fails closed with a distinct wall-clock timeout after Nm error — separate from the existing no usable result fail-close, so log readers can immediately tell which mode tripped and whether to bump the timeout or investigate the engine.
  • Docs: README inputs row + a commented # timeout-minutes: "20" in the example workflow.

Behavior change

Consumers whose reviews previously took 20+ minutes will now fail closed at 20 minutes instead of running to completion (or eventual engine failure). The error message tells them to bump timeout-minutes in their workflow. Motivation: a large-PR + slow-model combo was observed running 43 minutes before failing closed on subtask timeouts; a hard ceiling makes the failure mode predictable (fail fast, clear message) and stops burning quota on runs that were going to fail anyway.

Notes

  • Accepts decimals (e.g. "0.5" = 30 seconds) for testing.
  • In exhaustive mode each engine pass has its own budget, so worst-case whole-review wall time = timeout-minutes × 3.
  • No input/output signature changes beyond the new timeout-minutes; existing workflows keep working with the 20-minute default.
Assets 2
Loading