Skip to content

Fix flaky tenant input validations in different Python versions #1355

@tsmith023

Description

@tsmith023

In Python3.12, it is certain that the logic used when validating the inputs for tenant CRUD methods can flake perhaps due to how Python performs these typing validations under-the-hood. This may be indicative of a bug in Python but we should fix it by avoiding this flaky behaviour:

"""
weaviate.exceptions.WeaviateInvalidInputError: Invalid input provided: Argument 'tenants' must be one of:
[
  <class 'weaviate.collections.classes.tenants.Tenant'>,
  <class 'weaviate.collections.classes.tenants.TenantUpdate'>,
  typing.Sequence[
      typing.Union[weaviate.collections.classes.tenants.Tenant,
      weaviate.collections.classes.tenants.TenantUpdate]
    ]
], but got <class 'list'>.
"""

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinggood first issueGood for newcomers

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions