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
{{ message }}
Repository navigation
Integer maximum value is 9223372036854775807, but the value in the document is 9223372036854776000 #360
/chat/completions still uses application/json and #/components/schemas/CreateChatCompletionRequest" schema for its requestBody. That still poses a problem with serializing.
The January fix and subsequent regression history from this report have been preserved in #464, alongside the existing Swift reproduction from #445. Both reports concern the same remaining Chat Completions seed bounds.
Closing this issue as a duplicate, not as resolved. The rounded bounds remain in the reviewed published specification, and #464 remains open for the repair and validation.
Correction to the duplicate closure above: only this report's seed-bound finding has been consolidated into #464. The May 11 serialization comment does not provide enough detail to determine whether it is the same problem, and the seed repair must not be treated as resolving it.
The exact seed bounds are now in published revision fda2733. @mys721tx, could you share a minimal request/schema reproduction, the serializer or generator name and version, and the complete error? Please remove credentials and personal data. Reopening this report so that the unresolved serialization context is not lost; this is not yet confirmation of a distinct serializer defect.
Activity
janodev commentedon Jan 30, 2025
This was addressed in d78fe2a see line 14831 and 14198.
mys721tx commentedon May 11, 2025
/chat/completionsstill usesapplication/jsonand#/components/schemas/CreateChatCompletionRequest"schema for itsrequestBody. That still poses a problem with serializing.markstuart-oai commentedon Sep 22, 2026
Duplicate of #464.
The January fix and subsequent regression history from this report have been preserved in #464, alongside the existing Swift reproduction from #445. Both reports concern the same remaining Chat Completions
seedbounds.Closing this issue as a duplicate, not as resolved. The rounded bounds remain in the reviewed published specification, and #464 remains open for the repair and validation.
markstuart-oai commentedon Sep 23, 2026
Correction to the duplicate closure above: only this report's seed-bound finding has been consolidated into #464. The May 11 serialization comment does not provide enough detail to determine whether it is the same problem, and the seed repair must not be treated as resolving it.
The exact seed bounds are now in published revision fda2733. @mys721tx, could you share a minimal request/schema reproduction, the serializer or generator name and version, and the complete error? Please remove credentials and personal data. Reopening this report so that the unresolved serialization context is not lost; this is not yet confirmation of a distinct serializer defect.
markstuart-oai commentedon Sep 23, 2026
Closure check: the seed-bound finding is fixed in published OpenAPI revision fda2733d54c35878cee469d2a7c5cfafb22914f5, with the same exact bounds in JSON; #464 is now closed as fixed.