fix: avoid double-counting fetch failures #33

Merged
MrSphay merged 2 commits from codex/issue-15-fetch-metrics into codex/production-intelligence-terminal 2026-05-17 15:59:29 +00:00
Owner

Addresses #15.\n\nChanges:\n- Records exactly one fetch metric per network attempt in safeFetch and safeFetchText.\n- Preserves HTTP failure status, body byte count, duration, and error text without a second catch metric.\n- Records HTML/non-JSON 200 responses as failed JSON-shape errors instead of successful fetches.\n- Adds regression coverage for HTTP failure, HTML response, and retry attempt accounting.\n\nValidation:\n- git diff --check (only Windows CRLF warnings).\n- Runner-only constraint honored; no local npm/node tests executed.

Addresses #15.\n\nChanges:\n- Records exactly one fetch metric per network attempt in safeFetch and safeFetchText.\n- Preserves HTTP failure status, body byte count, duration, and error text without a second catch metric.\n- Records HTML/non-JSON 200 responses as failed JSON-shape errors instead of successful fetches.\n- Adds regression coverage for HTTP failure, HTML response, and retry attempt accounting.\n\nValidation:\n- git diff --check (only Windows CRLF warnings).\n- Runner-only constraint honored; no local npm/node tests executed.
MrSphay added 1 commit 2026-05-17 12:40:16 +00:00
fix: avoid double-counting fetch failures
All checks were successful
Codex Template Compliance / template-compliance (pull_request) Successful in 6s
Build / test-and-image (pull_request) Successful in 49s
08d24594c1
MrSphay added 1 commit 2026-05-17 15:56:16 +00:00
Merge branch 'codex/production-intelligence-terminal' into codex/issue-15-fetch-metrics
All checks were successful
Codex Template Compliance / template-compliance (pull_request) Successful in 5s
Build / test-and-image (pull_request) Successful in 55s
18b2e61678
MrSphay merged commit e0345e2de3 into codex/production-intelligence-terminal 2026-05-17 15:59:29 +00:00
MrSphay deleted branch codex/issue-15-fetch-metrics 2026-05-17 15:59:30 +00:00
Sign in to join this conversation.