Skip to content

Return a failure status from doctor checks#12

Open
juliosuas wants to merge 1 commit into
mainfrom
agent/doctor-schema-contract
Open

Return a failure status from doctor checks#12
juliosuas wants to merge 1 commit into
mainfrom
agent/doctor-schema-contract

Conversation

@juliosuas

Copy link
Copy Markdown
Owner

What changed

  • make ghost doctor return exit status 1 when a hard-error check fails
  • preserve both JSON and human-readable output before exiting
  • cover both CLI output modes with regression tests

Why

Hard-error doctor checks were rendered correctly but still returned a successful process status, so scripts could not distinguish healthy output from a failed diagnostic.

Proof

  • .venv/bin/python -m ruff check ghost tests
  • .venv/bin/python -m ruff format --check ghost tests
  • .venv/bin/python -m pytest -q (59 passed)
  • Terminal output behavior is covered in tests/test_investigator.py

Safety

  • This supports authorized security research, journalism, law enforcement, or self-audits
  • No private target data, secrets, generated databases, reports, or investigation artifacts are committed
  • No new collection behavior is introduced

@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 57 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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

Run ID: bb2eac14-40a4-41e1-97ba-8ecdf50798df

📥 Commits

Reviewing files that changed from the base of the PR and between b1792a3 and a0d9e46.

📒 Files selected for processing (2)
  • ghost/ui/cli.py
  • tests/test_investigator.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch agent/doctor-schema-contract

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.

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