Skip to content

Integer maximum value is 9223372036854775807, but the value in the document is 9223372036854776000 #360

Closed

Description

@atacan
seed:
  type: integer
  minimum: -9223372036854776000
  maximum: 9223372036854776000
  nullable: true
  description: >

Activity

  1. janodev commented on Jan 30, 2025

    @janodev

    This was addressed in d78fe2a see line 14831 and 14198.

  2. mys721tx commented on May 11, 2025

    @mys721tx

    /chat/completions still uses application/json and #/components/schemas/CreateChatCompletionRequest" schema for its requestBody. That still poses a problem with serializing.

  3. added
    bugSomething isn't working
    specificationOpenAPI contract, authored schema, or specification publication defects.
    on Sep 6, 2026
  4. markstuart-oai commented on Sep 22, 2026

    @markstuart-oai
    Contributor

    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 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.

  5. markstuart-oai commented on Sep 23, 2026

    @markstuart-oai
    Contributor

    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.

  6. markstuart-oai commented on Sep 23, 2026

    @markstuart-oai
    Contributor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

bugSomething isn't workingspecificationOpenAPI contract, authored schema, or specification publication defects.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions