Skip to content

[Schema Inaccuracy] Consider making Workflow ID int64 to future-proof against overflow #4512

Open
@caleblloyd

Description

@caleblloyd

Consider changing the Workflow ID parameter and model to use int64 instead of int. A recent Workflow I created got the ID of around 141,000,000 which is still a ways from int.MaxValue of 2,147,483,647. But given enough time and more users making workflows this could eventually overflow.

Schema Inaccuracy

  • #/components/parameters/workflow-id - Consider that int32 may overflow in the future. Add format: int64
  • #/components/schemas/workflow/id - Consider that int32 may overflow in the future. Add format: int64

Expected

No overflow

Reproduction Steps

No current overflow, so no reproduction. However

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions