Repository navigation
Surface chat system_fingerprint and logprobs as response metadata #1104
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
PratikDhanave (PratikDhanave)
wants to merge
4
commits into
microsoft:main
Choose a base branch
from
PratikDhanaveFork:fix/openai-chat-response-metadata
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
8aa128d
Surface chat system_fingerprint and logprobs as response metadata
PratikDhanave 51552c4
Address review: accumulate streaming chat logprobs across chunks
PratikDhanave ecbf3ca
Merge remote-tracking branch 'upstream/main' into fix/openai-chat-res…
PratikDhanave fe81313
Merge remote-tracking branch 'upstream/main' into fix/openai-chat-res…
PratikDhanave File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Parity issue:
SystemFingerprint/Logprobsare scoped to the message, not the responseBecause this update sets
MessageID: resp.ID(non-empty) alongsideAdditionalProperties,Response.Update(seeagent/response.go's own doc comment: "A non-empty MessageID scopes these properties to that message. Otherwise, they are response-level properties.") copiesSystemFingerprint/Logprobsintomsg.AdditionalProperties, notresp.AdditionalProperties. The PR's own test (lastMessageAdditionalProperties) confirms this — it has to scanresp.Messagesrather than readingresp.AdditionalProperties.Upstream Python treats both as response-level metadata:
_get_metadata_from_chat_response/_get_metadata_from_chat_choicepopulate a singleresponse_metadatadict that is passed asChatResponse(..., additional_properties=response_metadata, ...)(_chat_completion_client.pylines ~879-904, 1007-1022), never on an individualMessage.This same provider package already has the correct pattern for this exact situation:
responsesPopulateAdditionalPropertiesinprovider/openaiprovider/responses.go(around line 1265) explicitly yields the message-bearing update first, then emits a second, metadata-only update with an emptyMessageIDso the properties land onResponse.AdditionalPropertiesinstead of the message.Suggested fix: follow the same split used in
responses.go— yield the content-bearing update withMessageIDset, then emit a follow-up update (or restructure this single update) withMessageIDunset soSystemFingerprint/Logprobsland inResponse.AdditionalProperties, matching Python'sChatResponse.additional_propertiessemantics. The same issue applies to the streaming path at line 250.