Skip to content

docs(item4): confirm the served_model/phase telemetry fix landed and works - #1868

Merged
seonghobae merged 5 commits into
mainfrom
docs/item4-served-model-fix-confirmed
Sep 5, 2026
Merged

docs(item4): confirm the served_model/phase telemetry fix landed and works#1868
seonghobae merged 5 commits into
mainfrom
docs/item4-served-model-fix-confirmed

Conversation

@seonghobae

@seonghobae seonghobae commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

Summary

Item 4's gap-baseline entry named a still-needed fix: scripts/ci/noema_review_gate.py's call_llm caught urllib.error.HTTPError without reading the response body, so it couldn't surface the gateway's served_model/error detail. That fix shipped: #1831 ("ground verdicts and classify gateway errors," merged), hardened by #1835 and #1850.

Found incidentally while handling an unrelated Autofix event on PR #1757: a fresh gateway failure now logs phase=response_error and a real model name (served_model=google/gemma-4-31b-it) instead of the old unknown/generic-phase pair. The underlying gateway instability (502 after 284.7s) is still a separate, open, recurring problem — but the telemetry gap that made every prior instance of it undiagnosable is closed.

Test plan

  • python3 -m pytest tests/test_product_technical_gap_baseline.py -q — 5 passed

🤖 Generated with Claude Code

Summary by CodeRabbit

  • 문서
    • HTTP 오류 텔레메트리 수정 사항과 운영 검증 결과를 기준 문서에 추가했습니다.
    • 게이트웨이 오류 발생 시 실제 제공 모델 정보가 기록되도록 반영된 내용을 명시했습니다.
    • 운영 로그에서 모델 정보가 확인된 사례를 추가했습니다.
    • 게이트웨이 502 오류는 아직 해결되지 않은 문제로 기록했습니다.

…works

The .github-side follow-up this entry named as still-needed (call_llm not
reading the HTTPError response body, so it couldn't surface served_model)
shipped in #1831 (merged), hardened by #1835 and #1850.

Found incidentally while handling an unrelated Autofix event on PR #1757: a
fresh gateway failure now logs phase=response_error and a real model name
(served_model=google/gemma-4-31b-it) instead of the old unknown/connecting
pair. The underlying gateway instability (502 after 284.7s) is still a
separate, open, recurring problem -- but the telemetry gap that made every
prior instance of it undiagnosable is closed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Sep 4, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

Next included review available in 49 minutes.

Check out review usage here.

View limit details

Limit 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.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 3626656a-74e4-4f47-a974-d0205b91bb14

📥 Commits

Reviewing files that changed from the base of the PR and between db76b7e and 7a1fc1d.

📒 Files selected for processing (1)
  • docs/product-technical-gap-baseline.md

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Team

Run ID: 696102c9-5850-4b1b-9e40-91f95439358e

📥 Commits

Reviewing files that changed from the base of the PR and between b5efbc2 and db76b7e.

📒 Files selected for processing (1)
  • docs/product-technical-gap-baseline.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

HTTP 오류 텔레메트리의 단계 분류와 모델 귀속 결과를 기준선 문서에 추가했다. 운영 로그에서 google/gemma-4-31b-it을 확인했으며, 502 게이트웨이 오류는 미해결 상태로 기록했다.

Changes

HTTP 오류 텔레메트리 기준선

Layer / File(s) Summary
텔레메트리 기준선 문서 갱신
docs/product-technical-gap-baseline.md
HTTPErrorresponse_error 단계로 분류하고 오류 응답 본문에서 served_model을 추출한 결과를 기록했다. 운영 로그에서 google/gemma-4-31b-it을 확인했으며, 502 게이트웨이 오류는 별도 미해결 문제로 남겼다.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to db76b

This updates the technical baseline with HTTP error telemetry behavior and validation results. No current merge-blocking risk remains.

Suggested reviewers: claude

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed 제목은 served_model 및 단계 텔레메트리 수정이 적용되었고 검증되었다는 주요 변경 사항을 정확하고 간결하게 설명합니다.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/item4-served-model-fix-confirmed

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.

@seonghobae
seonghobae enabled auto-merge (squash) September 5, 2026 02:27
@opencode-agent
opencode-agent Bot disabled auto-merge September 5, 2026 05:57
@seonghobae
seonghobae merged commit a01ffc1 into main Sep 5, 2026
17 of 25 checks passed
@seonghobae
seonghobae deleted the docs/item4-served-model-fix-confirmed branch September 5, 2026 09:06
seonghobae pushed a commit that referenced this pull request Sep 5, 2026
…grity rules

Both contributed by a reviewing session from measurements it made today,
not by this session. Recorded here because the catalog is the org's
shared store and a lesson only pays off when someone other than its
author can find it.

Signature 8 -- same-anchor merge conflicts. The collision unit for
append-heavy documents is the anchor, not the file. Measured on
docs/product-technical-gap-baseline.md: #1868 merged SECOND into the
same file and stayed clean because its hunk sat in a different region,
while #1903 broke on sharing #1868's anchor. So a path-level claim is
wrong in both directions -- it over-serializes PRs that would never have
touched and fails to warn the pair that actually conflicts. Also records
that `behind` is admin-mergeable with zero pushes while `dirty` is a
git-level conflict that cannot be bypassed (405), so the push-free path
exists for exactly one PR per anchor per round.

Measurement integrity, under the KPI table. `c=$(gh api ... || echo 0)`
turns a rate-limited call into a genuine-looking zero; in a real sweep
that produced impossible rows (in_progress_runs=13 with running_jobs=0
AND queued_jobs=0) which were briefly explained away as "the metric
oscillates" rather than read as the instrument breaking. Re-measured
without the mask: min 27 / max 36 / mean 32.1, stable. Three rules
follow: never let a failed call fall back to a countable value, treat a
self-contradictory row as the tell, and settle a disagreement about a
total by printing records rather than recounting.

Every KPI in this file is a script-produced count, so these belong beside
the table rather than in a separate note.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BV96rXhqoR3tYZ9AeAVur4
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