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
Fix flaky tenant input validations in different Python versions #1355
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'>."""
Activity
Nitish-Kshatriya-P commentedon Nov 5, 2025
I believe that this issue is fixed, can someone close this ticker/issue?
fix: resolve flaky tenant input validation in Python 3.12 (weaviate#1355
databyjp commentedon Nov 3, 2026
Addressed by #2108