diagnose(ci): isolate Bytez discovery 500 - #1472
Conversation
Record only HTTP status codes for bounded authenticated Bytez catalog variants; never emit response bodies or credential metadata. Signed-off-by: Seongho Bae <me@seonghobae.me> Commit-Message-Assisted-by: Claude (via Claude Code)
|
Warning Review limit reachedNext included review available in 33 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
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. Comment |
Signed-off-by: Seongho Bae <me@seonghobae.me> Commit-Message-Assisted-by: Claude (via Claude Code)
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| except (OSError, TimeoutError, urllib.error.URLError) as exc: | ||
| code = type(exc).__name__ |
There was a problem hiding this comment.
🟡 Diagnostic response aborts every review
If Bytez returns a malformed HTTP response, urlopen raises an uncaught protocol exception and aborts sidecar provisioning. Every dependent review then fails before model discovery.
Prompt for agents
Keep the temporary Bytez diagnostic observational and non-fatal. In scripts/ci/contextual_orchestrator_review_sidecar.sh, handle http.client.HTTPException from urllib.request.urlopen alongside the existing network exceptions, emit only its exception type as the diagnostic value, and add a contract or executable test proving a malformed HTTP response cannot abort sidecar provisioning.
Was this helpful? React with 👍 or 👎 to provide feedback.
Signed-off-by: Seongho Bae <me@seonghobae.me> Commit-Message-Assisted-by: Claude (via Claude Code)
Run the status-only requests solely for PR 1473 so ordinary review sidecars remain unchanged. Signed-off-by: Seongho Bae <me@seonghobae.me> Commit-Message-Assisted-by: Claude (via Claude Code)
… into diagnose/bytez-discovery-status
|
|
||
| # Temporary PR-only diagnostic: emit status codes, never response bodies or | ||
| # credential metadata, to isolate Bytez's persistent authenticated HTTP 500. | ||
| if [ "${PR_NUMBER:-}" = "1473" ] && [ -n "${BYTEZ_API_KEY:-}" ]; then |
There was a problem hiding this comment.
🟡 Unrelated pull requests trigger diagnostics
Any repository's pull request 1473 satisfies PR_NUMBER without a repository check. Its reviews send four unintended Bytez requests and can add two minutes.
| if [ "${PR_NUMBER:-}" = "1473" ] && [ -n "${BYTEZ_API_KEY:-}" ]; then | |
| if [ "${TARGET_REPOSITORY:-${GITHUB_REPOSITORY:-}}" = "ContextualWisdomLab/.github" ] && [ "${PR_NUMBER:-}" = "1473" ] && [ -n "${BYTEZ_API_KEY:-}" ]; then |
Was this helpful? React with 👍 or 👎 to provide feedback.
1 participant
Controlled diagnostic change. The status-only Bytez probe runs only when PR_NUMBER is 1473; ordinary sidecars are unchanged. After #1472 lands, #1473 will trigger the trusted main script and both PRs will be closed/reverted once evidence is captured.