You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The OpenAI library is tracking all received properties and storing them into a SerializedAdditionalRawData dictionary. It doesn't publicly expose this data, except via InternalsVisibleTo to Azure.AI.OpenAI.
Why is Azure.AI.OpenAI special here, such that this data is only available to that specific library?
Steps to reproduce
Try to access additional properties sent down as part of an OpenAI-compatible response. You can't.
Code snippets
No response
OS
Any
.NET version
Any
Library version
2.1.0-beta
The text was updated successfully, but these errors were encountered:
I understand everything is beta and preview and "happening". But I'm just saying that the "you've been rate limited" failure information is extra important for those using realtime with only 100 RPD Thanks for your time.
ConversationResponseFinishedUpdate.StatusDetails.SerializedAdditionalRawData
{{"type":"requests","code":"rate_limit_exceeded","message":"Rate limit reached for
gpt-4o-realtime-preview in organization org-XXXXXXXXXXXXXXXXXXXXXXXXXX on requests
per day (RPD): Limit 100, Used 100, Requested 1. Please try again in 14m24s.
Visit https://platform.openai.com/account/rate-limits to learn more."}}
Service
OpenAI
Describe the bug
openai-dotnet/src/OpenAI.csproj
Lines 54 to 57 in ef201cd
The OpenAI library is tracking all received properties and storing them into a SerializedAdditionalRawData dictionary. It doesn't publicly expose this data, except via InternalsVisibleTo to Azure.AI.OpenAI.
Why is Azure.AI.OpenAI special here, such that this data is only available to that specific library?
Steps to reproduce
Try to access additional properties sent down as part of an OpenAI-compatible response. You can't.
Code snippets
No response
OS
Any
.NET version
Any
Library version
2.1.0-beta
The text was updated successfully, but these errors were encountered: