fix(ruby): use correct SDK_ID_RUBY_PROVIDER for telemetry#328
Merged
Conversation
The Ruby provider was incorrectly reporting SDK_ID_PYTHON_PROVIDER instead of SDK_ID_RUBY_PROVIDER in its resolve API calls. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
fabriziodemaria
force-pushed
the
fix/ruby-sdk-id
branch
from
77594ff to
6c093d1
Compare
nicklasl
approved these changes
Mar 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
SDK_ID_PYTHON_PROVIDER(enum value 6) instead ofSDK_ID_RUBY_PROVIDER(enum value 8) in its resolve API callsTest plan
make testpasses for the Ruby providerSDK_ID_RUBY_PROVIDERin thesdk.idfield🤖 Generated with Claude Code