Skip to content

fix: keep Pingora diagnostics payload-free - #31

Open
seonghobae wants to merge 40 commits into
fix/fail-closed-http1-upgrade-v1from
fix/payload-safe-pingora-logging-v1
Open

fix: keep Pingora diagnostics payload-free#31
seonghobae wants to merge 40 commits into
fix/fail-closed-http1-upgrade-v1from
fix/payload-safe-pingora-logging-v1

Conversation

@seonghobae

@seonghobae seonghobae commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Valid finding

The gateway's canonical observability target is payload-free, but both production composition roots previously installed env_logger directly from operator RUST_LOG. At the pinned Pingora revision, supplier diagnostics include request-derived material before the CWL request callback. Broad operator diagnostics could therefore bypass the process data-minimization invariant.

Fixes #30.

RED → causal fix

Historical RED f31987fb92d5b8b24a7286db6e1702b54c472898 added compiled-process acceptance under RUST_LOG=trace: the origin must receive URI/query/Host/Authorization/Cookie sentinels while process stderr contains none of them.

The retained fix introduces one shared logging_policy used by both production composition roots. Operator level/target selection is preserved, but Pingora-family dependency record messages are replaced with a static marker before env_logger formats them. CWL-owned bounded observability remains unchanged. Product/consumer logging, auth/business logic, routing, Wardnet/EgressWeave policy and Keyverse identity remain outside this boundary.

Fixture hardening retains simultaneous traffic/metrics reservations, five-second/64 KiB origin bounds, exact request target and HTTP-field identity, exact completion-line and Prometheus oracles, and post-readiness marker-count increase so startup diagnostics cannot manufacture non-vacuity.

Ordinary/non-force succession

Final #29 084ef0fd8c5cf2e55dccffd23961933270347925 is the exact parent. Ordinary two-parent bf0a5fcd265c100b18a446d0718c9163ae90a946 preserved historical #31 while adopting the final #29 tree and reapplying only the valid logging delta. No force-push, destructive rebase, stale-parent source, or predecessor receipt was replayed.

Hosted RED → repair → exact closure

Exact 985d4df311c93966a5ef4a8212c89f1d249dd652 first exposed Rust 1.98.0 formatting only; 468e8b2fec322b67be61aa511d1616a4de52c3f6 applied the formatter-prescribed layout. A later exact head passed formatting/compile/tests but failed the mandatory 100% owned-production coverage gate only at PayloadSafeLogger::enabled; 4d901f89c8e38195af8d9ac3efb0f089cb15df8b added a focused unit contract proving exact filter delegation without weakening coverage.

The later CodeRabbit review reported touched-function Docstring Coverage below the repository expectation. Documentation-only descendants through final 8230f8d1311adccc133b7f6ed86df441533e486c add constraint/evidence-oriented rustdoc to the touched logging/composition-root/fixture helpers without changing runtime behavior.

Final exact #31 head is 8230f8d1311adccc133b7f6ed86df441533e486c and is unchanged through closure:

  • CI 34251472731: terminal success on this exact SHA.
  • Supply Chain 34251472751: terminal success on this exact SHA.
  • Exact-head owner technical COMMENT review reports no actionable source, test or documentation finding. It remains technical evidence only, not an independent human APPROVED governance decision.

#33 has now ordinary/non-force adopted this unchanged final #31 tree and must independently reacquire its own exact-head hosted/current-range evidence. No #31 receipt transfers to that changed child.

Keep Draft. Supplier #54/#62, #56 independent approval, protected integration, immutable release, canary/cutover, rollback and legacy removal remain separate earlier/later gates. No self-approval, force-push/destructive rebase, gate weakening or predecessor-evidence transfer is claimed.

@coderabbitai

coderabbitai Bot commented Sep 2, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: f85e80e6-5394-4303-9e43-302beb1e13a0

📥 Commits

Reviewing files that changed from the base of the PR and between 084ef0f and 985d4df.

📒 Files selected for processing (13)
  • CHANGELOG.md
  • Cargo.toml
  • OPERABILITY.md
  • SECURITY.md
  • TEST_STRATEGY.md
  • THREAT_MODEL.md
  • docs/doctoring/TRACEABILITY.md
  • docs/product-technical-gap-baseline.md
  • src/bin/cwl-pingora-gateway.rs
  • src/bin/cwl-pingora-pg-erd-migration.rs
  • src/lib.rs
  • src/logging_policy.rs
  • tests/pingora_diagnostic_log_safety.rs

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


📝 Walkthrough

Walkthrough

프로세스 전역 logging_policy가 Pingora 계열 로그 본문을 정적 마커로 치환합니다. 두 프로덕션 바이너리가 새 정책을 설치합니다. 컴파일 회귀 테스트가 민감한 요청 전달과 stderr 비노출을 검증합니다. 관련 보안·운영·릴리스 문서도 갱신되었습니다.

Changes

Payload-safe 로깅

Layer / File(s) Summary
로깅 정책 구현 및 런타임 설치
Cargo.toml, src/lib.rs, src/logging_policy.rs, src/bin/cwl-pingora-gateway.rs, src/bin/cwl-pingora-pg-erd-migration.rs
PayloadSafeLogger가 Pingora 계열 로그 본문을 정적 마커로 치환합니다. 두 바이너리는 init_runtime_logging()을 사용합니다.
진단 로그 회귀 검증
tests/pingora_diagnostic_log_safety.rs
RUST_LOG=trace에서 URI, Host, Authorization, Cookie 값이 origin에 전달되는지 확인합니다. Pingora 진단 로그의 마스킹과 stderr 내 비밀값 부재도 확인합니다.
정책 및 릴리스 증거 갱신
CHANGELOG.md, SECURITY.md, OPERABILITY.md, TEST_STRATEGY.md, THREAT_MODEL.md, docs/doctoring/TRACEABILITY.md, docs/product-technical-gap-baseline.md
프로세스 전역 로그 보호 범위와 검증 조건을 문서화합니다. HTTP/1 전환 제한, 위협 모델, 추적성, 릴리스 기준을 현재 상태에 맞게 갱신합니다.

Priority: ➖ Normal — Schedule the payload-safe logging change because Pingora diagnostics can expose request URIs and sensitive headers across both production gateway binaries.

Estimated code review effort: 4 (Complex) | ~45 minutes

Severity of issue fixed: Medium

Merge Risk: ⚪ Minimal · up to 985d4

The gateway preserves request delivery and safe application observability while preventing Pingora diagnostic logs from exposing request-derived secrets.

Sequence Diagram(s)

sequenceDiagram
  participant Test
  participant Gateway
  participant Origin
  participant Logger
  Test->>Gateway: Start with RUST_LOG=trace
  Test->>Gateway: Send request with sensitive values
  Gateway->>Origin: Forward request unchanged
  Origin-->>Gateway: Return 200 response
  Gateway->>Logger: Emit Pingora diagnostic record
  Logger-->>Test: Write redacted marker to stderr
  Test->>Logger: Check marker and absence of sensitive values
Loading
🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Linked Issues check ⚠️ Warning 공유 로거 적용, Pingora 메시지 본문 마스킹, CWL 로그 수준 보존, 컴파일 프로세스 기반 비밀값 회귀 테스트는 Issue #30의 핵심 코딩 목표를 충족합니다. 그러나 PR 설명에 exact-head CI, coverage, rustdoc, OCI, security, supply-chain 및 기술 검토 증거가 아직 완료되지 않았고 Rust 테스… Issue #30의 잔여 요구사항을 완료하고 exact-head CI, coverage, rustdoc, OCI, security, supply-chain 및 기술 검토 결과를 첨부하십시오. Rust 테스트와 새 회귀 테스트도 실행하여 결과를 확인하십시오.
Docstring Coverage ⚠️ Warning Docstring coverage is 46.15% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 26 functions across 5 files. (8 skipped: … Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (3 passed)
Check name Status Explanation
Out of Scope Changes check ✅ Passed 변경 사항은 Issue #30의 프로세스 전역 Pingora 진단 로그 마스킹, 회귀 테스트, 의존성 설정 및 관련 운영·보안·위협 모델·추적성 문서에 직접 연결됩니다. 라우팅, 인증, 비즈니스 권한과 무관한 변경은 확인되지 않습니다.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed PR 제목은 Pingora 진단 메시지의 payload 차단이라는 핵심 변경을 정확하고 간결하게 설명합니다.
Full details: Linked Issues check

Explanation

공유 로거 적용, Pingora 메시지 본문 마스킹, CWL 로그 수준 보존, 컴파일 프로세스 기반 비밀값 회귀 테스트는 Issue #30의 핵심 코딩 목표를 충족합니다. 그러나 PR 설명에 exact-head CI, coverage, rustdoc, OCI, security, supply-chain 및 기술 검토 증거가 아직 완료되지 않았고 Rust 테스트도 실행되지 않았다고 명시되어 있습니다. Issue #30은 이 증거를 merge/release 전에 요구합니다.

Full details: Docstring Coverage

Explanation

Docstring coverage is 46.15% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 26 functions across 5 files. (8 skipped: 8 unsupported.)

  • Fix all pre-merge checks with AI
✨ Finishing Touches 💡 2
📝 Generate docstrings 💡
  • Create stacked PR
  • Commit on current branch
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/payload-safe-pingora-logging-v1

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.

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

Please review the ordinary-restacked exact range 084ef0fd8c5cf2e55dccffd23961933270347925..985d4df311c93966a5ef4a8212c89f1d249dd652. Focus on the process-global logging boundary, Pingora target classification/redaction, the compiled secret-bearing request non-vacuity oracle, and any stale-parent regression after the two-parent adoption. This request is for technical findings only; it is not an approval/governance substitute.

@coderabbitai

coderabbitai Bot commented Sep 8, 2026

Copy link
Copy Markdown
🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

base='084ef0fd8c5cf2e55dccffd23961933270347925'
head='985d4df311c93966a5ef4a8212c89f1d249dd652'

printf '%s\n' '== Exact commits and ancestry =='
git show -s --format='%H%nparents: %P%nsubject: %s' "$base" "$head"
printf '\n== Merge base and ancestry checks ==\n'
git merge-base "$base" "$head"
git merge-base --is-ancestor "$base" "$head" && echo 'base_is_ancestor=true'
printf '\n== Changed paths ==\n'
git diff --name-status "$base..$head"
printf '\n== Diff statistics ==\n'
git diff --stat "$base..$head"

printf '\n== Rust file outlines in requested range ==\n'
git diff --name-only "$base..$head" -- '*.rs' |
while IFS= read -r f; do
  test -n "$f" || continue
  echo "--- $f"
  ast-grep outline "$f" --items all --view expanded || true
done

printf '\n== Relevant definitions and logger-installation call sites ==\n'
rg -n -C 4 --type rust \
  '(logging_policy|env_logger|set_logger|try_init|Builder::|Pingora|pingora|LogRecord|Record|diagnostic|redact)' \
  src tests 2>/dev/null || true

printf '\n== Relevant manifest dependency lines ==\n'
rg -n -C 2 '(env_logger|^log\s*=|pingora)' Cargo.toml

Length of output: 141978


🏁 Script executed:

#!/bin/bash
set -euo pipefail

base='084ef0fd8c5cf2e55dccffd23961933270347925'
head='985d4df311c93966a5ef4a8212c89f1d249dd652'

printf '%s\n' '== Exact changed implementation diff =='
git diff --find-renames --find-copies --unified=80 "$base..$head" -- \
  Cargo.toml src/lib.rs src/logging_policy.rs \
  src/bin/cwl-pingora-gateway.rs src/bin/cwl-pingora-pg-erd-migration.rs \
  tests/pingora_diagnostic_log_safety.rs

printf '\n== logging_policy.rs ==\n'
cat -n src/logging_policy.rs

printf '\n== Diagnostic test, full source ==\n'
cat -n tests/pingora_diagnostic_log_safety.rs

printf '\n== Every process logger setup call site ==\n'
rg -n -C 5 --type rust \
  '(env_logger::|init_runtime_logging\s*\(|set_logger\s*\(|set_boxed_logger\s*\(|try_init\s*\(|\.init\s*\(\))' \
  . -g '!target/**'

printf '\n== Previous composition-root logger setup ==\n'
git show "$base:src/bin/cwl-pingora-gateway.rs" | nl -ba | sed -n '1,80p'
git show "$base:src/bin/cwl-pingora-pg-erd-migration.rs" | nl -ba | sed -n '1,100p'

printf '\n== Available Pingora source directories and log target declarations ==\n'
find "$HOME/.cargo" -type f -path '*pingora*' -name '*.rs' -print 2>/dev/null |
  head -n 20 || true
rg -n -C 2 --glob '*.rs' \
  '(target:\s*"[^"]*pingora[^"]*"|target:\s*module_path!|log::(trace|debug|info|warn|error)!|(?:trace|debug|info|warn|error)!)' \
  "$HOME/.cargo/git/checkouts" 2>/dev/null | head -n 300 || true

Length of output: 52156


🏁 Script executed:

#!/bin/bash
set -euo pipefail

base='084ef0fd8c5cf2e55dccffd23961933270347925'
head='985d4df311c93966a5ef4a8212c89f1d249dd652'
adoption='bf0a5fcd265c100b18a446d0718c9163ae90a946'
pingora_rev='09696b51bc59315353d96686355861604d0bb48c'

printf '%s\n' '== Requested-range commit topology =='
git rev-list --reverse --parents "$base..$head"
printf '\n== Adoption commit ==\n'
git show -s --format='%H%nparents: %P%ntree: %T%nsubject: %s' "$adoption"
parents=($(git show -s --format='%P' "$adoption"))
printf 'parent_1_tree=%s\n' "$(git show -s --format='%T' "${parents[0]}")"
printf 'parent_2_tree=%s\n' "$(git show -s --format='%T' "${parents[1]}")"
printf 'adoption_tree=%s\n' "$(git show -s --format='%T' "$adoption")"
printf '\n== Adoption delta against each parent ==\n'
git diff --stat "${parents[0]}" "$adoption"
git diff --stat "${parents[1]}" "$adoption"

printf '\n== Merge base exact tree identity ==\n'
printf 'base_tree=%s\nhead_tree=%s\n' \
  "$(git show -s --format='%T' "$base")" "$(git show -s --format='%T' "$head")"

workdir="$(mktemp -d)"
trap 'rm -rf "$workdir"' EXIT
for path in \
  pingora-core/src/protocols/http/client.rs \
  pingora-proxy/src/proxy_h1.rs \
  pingora-proxy/src/lib.rs \
  pingora-core/src/lib.rs
do
  url="https://raw.githubusercontent.com/cloudflare/pingora/${pingora_rev}/${path}"
  out="$workdir/$(basename "$path")"
  if curl --fail --silent --show-error --location "$url" --output "$out"; then
    echo "--- $path"
    rg -n -C 3 '(trace!|debug!|info!|warn!|error!|target:)' "$out" || true
  else
    echo "--- unavailable: $path"
  fi
done

Length of output: 23281


@seonghobae Technical review completed for 084ef0fd8c5cf2e55dccffd23961933270347925..985d4df311c93966a5ef4a8212c89f1d249dd652.

I found no actionable technical findings.

Key checks:

  • Both production composition roots install the shared payload-safe process logger before configuration parsing and listener activation.
  • The target classifier covers pingora, pingora_*, and pingora::*. This covers the relevant pinned supplier crates, including pingora_proxy and pingora_core.
  • The pinned pingora_proxy source contains broad diagnostics that format request headers. The wrapper replaces the message before env_logger formats the record.
  • CWL observability records retain their own target and bounded message content.
  • The compiled-process test uses RUST_LOG=trace. It proves the origin receives the exact URI/query/Host/Authorization/Cookie sentinels.
  • The test snapshots the redaction-marker count after readiness probes. It then requires a new marker after the secret-bearing request completes. This prevents a readiness-only marker from satisfying the oracle.
  • The test uses exact request-line and status parsing checks. The completion assertion uses a line suffix, which rejects numeric-prefix lookalikes.
  • The requested base is the merge base and an ancestor of the head.
  • The adoption commit bf0a5fcd265c100b18a446d0718c9163ae90a946 has the stated two parents. Its tree equals the final-fix: fail closed on uncharacterized HTTP/1 Upgrade #29 second-parent tree, not the stale first-parent tree.

I did not execute the Rust test suite in this inspection environment.

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Copy link
Copy Markdown
Contributor Author

Exact-head CI RCA and forward repair — 2026-09-09 KST. CI run 34246262369 on 985d4df311c93966a5ef4a8212c89f1d249dd652 failed only at job 102129364574 cargo fmt --all -- --check; load-contract and OCI-runtime jobs plus Supply Chain 34246262394 were GREEN. The formatter identified five mechanical layouts in tests/pingora_diagnostic_log_safety.rs and no behavioral failure.

Forward commit 468e8b2fec322b67be61aa511d1616a4de52c3f6 applies exactly those rustfmt layouts to that one file. It does not change process diagnostics, redaction sentinels, deadlines, assertions, dependencies, or product routing. Fresh exact-head CI and Supply Chain are required; keep Draft until terminal evidence and independent review.

Copy link
Copy Markdown
Contributor Author

Exact-head CI RCA and forward repair — 4d901f89c8e38195af8d9ac3efb0f089cb15df8b

The prior formatting repair passed compilation and every Rust test, but CI run 34247829130 correctly failed the owned-production 100% gate: src/logging_policy.rs:31-33 (PayloadSafeLogger::enabled) was the only uncovered production path, leaving logging_policy at 94.92% lines and the repository at 99.78%.

The new ordinary descendant adds one focused unit contract that executes enabled and verifies it delegates exactly to the configured inner filter. No production behavior changed in this second repair. Fresh CI and Supply Chain runs for this head are the authority; keep Draft until both are terminal GREEN and current-head independent approval exists.

@seonghobae
seonghobae marked this pull request as ready for review September 8, 2026 16:23

Copy link
Copy Markdown
Contributor Author

Review admission — exact head 4d901f89c8e38195af8d9ac3efb0f089cb15df8b

The two causal forward repairs are now verified on the unchanged head: CI run 34249033063 and Supply Chain run 34249033179 are terminal GREEN. The first repair applied only the required rustfmt layout; the second executed the previously uncovered PayloadSafeLogger::enabled delegation and closed the exact 100% coverage gap without changing production behavior.

Marked Ready for independent review. This remains a stacked PR targeting fix/fail-closed-http1-upgrade-v1; do not merge until the parent is integrated or the stack is ordinary-retargeted and a qualifying current-head approval exists.

@seonghobae
seonghobae marked this pull request as draft September 8, 2026 16:31

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

Please review the current exact head 8230f8d1311adccc133b7f6ed86df441533e486c, including the documentation-only repair for the prior touched-function Docstring Coverage warning. Do not transfer the earlier 985d4df... review receipt to this changed head.

@coderabbitai

coderabbitai Bot commented Sep 8, 2026

Copy link
Copy Markdown
🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

head='8230f8d1311adccc133b7f6ed86df441533e486c'
prior='985d4df311c93966a5ef4a8212c89f1d249dd652'

printf '%s\n' '== Exact head, ancestry, and range =='
git show -s --format='head=%H%nparents=%P%ntree=%T%nsubject=%s%n%nbody=%B' "$head"
printf '\nmerge_base_with_prior='
git merge-base "$prior" "$head"
git merge-base --is-ancestor "$prior" "$head" && echo 'prior_is_ancestor=true' || echo 'prior_is_ancestor=false'
printf '\n== Commits after prior reviewed head ==\n'
git log --reverse --format='%H %P%n%s%n%b%n---' "$prior..$head"
printf '\n== Changed paths after prior reviewed head ==\n'
git diff --name-status "$prior..$head"
printf '\n== Diff after prior reviewed head ==\n'
git diff --find-renames --find-copies --unified=60 "$prior..$head"

printf '\n== Rust structure at exact head ==\n'
for path in src/logging_policy.rs src/lib.rs src/bin/cwl-pingora-gateway.rs src/bin/cwl-pingora-pg-erd-migration.rs tests/pingora_diagnostic_log_safety.rs; do
  if test -f "$path"; then
    echo "--- $path"
    ast-grep outline "$path" --items all --view expanded || true
  fi
done

printf '\n== Logging policy, composition roots, and test source ==\n'
for path in src/logging_policy.rs src/bin/cwl-pingora-gateway.rs src/bin/cwl-pingora-pg-erd-migration.rs tests/pingora_diagnostic_log_safety.rs; do
  if test -f "$path"; then
    echo "--- $path"
    cat -n "$path"
  fi
done

printf '\n== All global logger installation sites ==\n'
rg -n -C 4 --type rust \
  '(?:env_logger::|init_runtime_logging\s*\(|set_logger\s*\(|set_boxed_logger\s*\(|try_init\s*\(|\.init\s*\(\))' \
  . -g '!target/**' || true

printf '\n== Doc-comment locations for touched functions ==\n'
rg -n -C 3 --type rust '^\s*///|^\s*pub\s+(?:\(crate\)\s+)?(?:fn|struct|enum|trait|mod)\b|^\s*fn\b' \
  src/logging_policy.rs tests/pingora_diagnostic_log_safety.rs 2>/dev/null || true

printf '\n== Merge topology from original base ==\n'
git rev-list --reverse --parents 084ef0fd8c5cf2e55dccffd23961933270347925.."$head"

Length of output: 83803


🏁 Script executed:

#!/bin/bash
set -euo pipefail

head='8230f8d1311adccc133b7f6ed86df441533e486c'
prior='985d4df311c93966a5ef4a8212c89f1d249dd652'

printf '%s\n' '== Patch validation =='
git diff --check "$prior..$head"
git diff --check 084ef0fd8c5cf2e55dccffd23961933270347925.."$head"

printf '\n== Individual forward commits ==\n'
for commit in $(git rev-list --reverse "$prior..$head"); do
  echo "--- $(git show -s --format='%H %s' "$commit")"
  git show --format= --find-renames --find-copies --unified=12 "$commit"
done

printf '\n== File-level history after previous head ==\n'
git log --format='%H %s' "$prior..$head" -- \
  src/bin/cwl-pingora-gateway.rs \
  src/bin/cwl-pingora-pg-erd-migration.rs \
  src/logging_policy.rs \
  tests/pingora_diagnostic_log_safety.rs

printf '\n== Pull request metadata and exact-head checks ==\n'
gh pr view 31 --repo ContextualWisdomLab/pingora-gateway \
  --json number,state,isDraft,baseRefName,baseRefOid,headRefName,headRefOid,statusCheckRollup \
  || true

Length of output: 27953


@seonghobae Technical review completed for exact head 8230f8d1311adccc133b7f6ed86df441533e486c.

I found no actionable technical findings.

Key checks:

  • I reviewed the current head independently. I did not transfer the 985d4df... review receipt.
  • The prior head is an ancestor and the merge base of the current head.
  • The forward range contains rustfmt-only changes, one focused PayloadSafeLogger::enabled delegation test, and documentation comments.
  • The documentation repair accurately describes the logging, startup-failure, and compiled-fixture boundaries. It does not change behavior.
  • Both production composition roots still install init_runtime_logging() before configuration parsing and listener activation.
  • PayloadSafeLogger still preserves the configured env_logger filter and redacts Pingora-family message bodies before formatting.
  • The classifier still covers pingora, pingora_*, and pingora::*.
  • The compiled-process test still verifies origin delivery of the URI/query, Host, Authorization, and Cookie sentinels. It also requires a redaction-marker increase after the secret-bearing request.
  • git diff --check found no whitespace errors in either the forward range or the complete PR range.
  • The exact-head CI and Supply Chain checks were still in progress when inspected.
  • I did not execute the Rust test suite in this inspection environment.
⚠️ Action not completed

Review rate limited.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@seonghobae seonghobae left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Owner technical review on exact head 8230f8d1311adccc133b7f6ed86df441533e486c.

Reviewed the full retained #31 logging boundary and the changed range after the prior CodeRabbit-reviewed head. The new commits are documentation-only: they add constraint/evidence-oriented rustdoc to touched logging/composition-root/test helpers and do not alter emitted records, target classification, RUST_LOG filtering, request delivery, fixture time/byte bounds, traffic, routing, or security semantics. The compiled acceptance still proves exact secret-bearing origin delivery, post-readiness supplier-redaction activity, exact bounded completion vocabulary, and whole-stderr sentinel absence. No actionable source, test, or documentation finding remains from this exact-range technical review.

This COMMENT is technical evidence only. It is not an independent human APPROVED governance decision, and it does not transfer predecessor CI/Supply Chain receipts to this changed head. Exact 8230f8d... hosted CI/Supply Chain must still finish terminal GREEN before #33 succession.

seonghobae added a commit that referenced this pull request Sep 8, 2026

Copy link
Copy Markdown
Contributor Author

Review-admission rationale for exact head 8230f8d1311adccc133b7f6ed86df441533e486c: CI 34251472731 and Supply Chain 34251472751 are both terminal GREEN after the public-doc successors, and the current-range payload-safe logging/coverage review has no unresolved source finding. Marking Ready admits independent review; it is not approval or merge-readiness. Parent fix/fail-closed-http1-upgrade-v1 must integrate and this PR must be ordinarily retargeted before protected-main merge; no predecessor receipt transfers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working priority: high type: bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant