grpc: fix statsdTags in reconfigure response - #495
Conversation
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughThe reconfiguration event now uses the correctly cased ChangesgRPC reconfiguration
Estimated code review effort: 2 (Simple) | ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@test/agents/test-grpc-reconfigure.mjs`:
- Around line 170-174: Update the response normalization around bodyVal and the
earlier normalization to coerce values only when the corresponding field’s
expected val type is numeric. Preserve numeric-looking strings for statsd,
statsdBucket, and statsdTags, and avoid converting empty strings or other
string-typed fields through Number().
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: c793247a-4a52-4983-b19a-2e8890ff8bcf
📒 Files selected for processing (2)
agents/grpc/src/grpc_agent.cctest/agents/test-grpc-reconfigure.mjs
4469c47 to
98a1f37
Compare
The gRPC reconfigure response dropped `statsdTags` because `PopulateReconfigureEvent()` looked up the wrong config key. Harden the gRPC reconfigure test to assert response fields directly and to fail when expected config keys are missing from the response body.` Signed-off-by: Santiago Gimeno <santiago.gimeno@gmail.com> PR-URL: #495 Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
98a1f37 to
13c74c0
Compare
The gRPC reconfigure response dropped `statsdTags` because `PopulateReconfigureEvent()` looked up the wrong config key. Harden the gRPC reconfigure test to assert response fields directly and to fail when expected config keys are missing from the response body.` Signed-off-by: Santiago Gimeno <santiago.gimeno@gmail.com> PR-URL: #495 Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>

The gRPC reconfigure response dropped
statsdTagsbecausePopulateReconfigureEvent()looked up the wrong config key.Harden the gRPC reconfigure test to assert response fields directly and to fail when expected config keys are missing from the response body.`
Summary by CodeRabbit
Bug Fixes
statsdTagsvalue from the configuration.Tests