fix(recommendations): retain incomplete AWS survivors - #2129
Conversation
Report typed AWS completeness diagnostics while preserving valid rows during discovery and regional collection. Verify the real command and CSV path against synthetic SDK responses. Refs LeanerCloud/cloud-commitments-go#54
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. 0 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour. 📝 WalkthroughWalkthroughThe command now logs incomplete recommendation errors and processes recommendations returned with those errors. Tests cover helper behavior and command output across region-selection modes and recommendation-detail outcomes. ChangesRecommendation completeness
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to Valid recommendations are retained and reported when AWS returns incomplete results. No concrete merge-blocking defect is established; the required CI and security checks should still pass before merge. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 25.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 8 functions across 3 files. (1 skipped: 1 unsupported.)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Preserve the published provider pins while selecting the fixed SDK. The unchanged parent reproduces the advisory against the same frozen database used for passing source and command-binary scans.
|
Added the OTEL dependency repair at Independent exact-SHA macOS Go 1.26.6 verification passed the full race suite, 15 actual root-command/config-loader/SDK/CSV scenarios plus five helper cases using synthetic boundary fixtures, and the actual The new two-manifest repair received two independent staged reviews and an exact-commit review. The earlier functional change remains at |
Preserve valid AWS recommendation rows when the provider reports typed incomplete collections. Discovery and regional collection now report those diagnostics while retaining survivors; ordinary error handling is unchanged.
Refs LeanerCloud/cloud-commitments-go#54. The parent issue remains open until all consumer work is complete.
Verification: 15 connected CLI command scenarios exercise explicit, default and fallback selection with valid, mixed, all-invalid, empty and API-error SDK responses through CSV output. Five helper cases cover partial and all-invalid collections, ordinary errors, cancellation and deadlines. All 20 pass with race detection against committed SHA443c10cfd1ad191d54ab0dcf02c388d7f9dd5547. Parent and warning-removal probes fail at the intended assertions. Normal commit hooks pass. Independent gpt-6-astra review approved that exact SHA. These tests use synthetic AWS responses through the published adapter; no live cloud calls or purchases.
OpenTelemetry SDK security repair is being handled separately. Required CI and security gates must pass before merge.
Summary by CodeRabbit