Pierre Jeambrun

Thanks for reporting the bug. I think it had something to do with 0 beeing `falsy`. It is handled in #25610

Resolved in https://github.com/apache/airflow/pull/15277. Closing

@eladkal Thank you elad, I missed that part

He changed the semi column with a semi column followed by a space. It seems to work but I have some weird autocompletion problem after the first argument, I don't...

Working as expected on latest client version (2.5.1) and latest airflow (2.5.1). ```python # Get dag list dag_api_instance = dag_api.DAGApi(api_client) try: api_response = dag_api_instance.get_dags(limit=1) pprint(api_response) except airflow_client.client.OpenApiException as e: print("Exception...

Working as expected on latest client version (2.5.1): ```python # Get pool list pool_api_instance = pool_api.PoolApi(api_client) try: api_response = pool_api_instance.get_pools() pprint(api_response) except airflow_client.client.OpenApiException as e: print("Exception when calling PoolApi->get_pools: %s\n"...

This was solved here https://github.com/apache/airflow/pull/32887/files. We should add a pre-commit hook to prevent such wrong usage of the nullable property in the OpenAPI spec. More info [here](https://github.com/apache/airflow/pull/32887#discussion_r1281241900) about other ways...

Closing, solved in 2.7.0 same problem originating from wrong usage of the nullable property next to a $ref object. Feel free to re-open if needed. Release candidate available here for...

Closing, solved. Up to now we had to manually cherry pick some patches at released time. 2.7.0 does not have this issue.

`dag_id`, `state` and `external_trigger` are now read only. They should not be provided in the `DagRun` object. With the latest client (2.5.1) we can trigger dag runs like this: ```python...