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
All functions that end up calling kubernetes.client.api_client.call_api and their ancestors, have an async_req: bool argument that is used for asynchronous execution in a thread. This argument is missing from the stubs. Also ancestors of those functions (through kwargs) have that argument as well.
Currently, I get an error from pyright if I use the argument: Pyright: No parameter named "async_req" [reportGeneralTypeIssues]
So for instance all of these functions have that argument:
kubernetes.client.api.batch_v1_api.BatchV1Api.create_namespaced_job_with_http_info as does
All functions that end up calling
kubernetes.client.api_client.call_api
and their ancestors, have anasync_req: bool
argument that is used for asynchronous execution in a thread. This argument is missing from the stubs. Also ancestors of those functions (throughkwargs
) have that argument as well.Currently, I get an error from pyright if I use the argument:
Pyright: No parameter named "async_req" [reportGeneralTypeIssues]
So for instance all of these functions have that argument:
kubernetes.client.api.batch_v1_api.BatchV1Api.create_namespaced_job_with_http_info
as doeskubernetes.client.api.batch_v1_api.BatchV1Api.create_namespaced_job
kubernetes.client.api.batch_v1_api.BatchV1Api.read_namespaced_job_status_with_http_info
kubernetes.client.api.batch_v1_api.BatchV1Api.read_namespaced_job_status
The text was updated successfully, but these errors were encountered: