shahar1 commented on issue #57826: URL: https://github.com/apache/airflow/issues/57826#issuecomment-6398196965
> According to the recent discussion about `airflowctl` 0.1.6 release on dev@: https://lists.apache.org/thread/7ocgsn7lzxnnbmfopyt6ko5wvkrm7rcn > > I ran the existing airflowctl integration tests from `airflow-ctl/v0-1-test` (what becomes 0.1.6) against the released images `apache/airflow:3.2.2`, `3.3.2` and `3.4.0b2`. Each run has 151 tests. What I found: > > * 3.4.0b2: `assets list` and `assets get` fail with `extra_forbidden` on `team_name`. > [UI: Show owning team in asset dependency popovers #71446](https://github.com/apache/airflow/pull/71446) added this field to asset reference models that use `StrictBaseModel`, so the branch's generated models reject it. Main already has the field, so only the release branch is affected. > * 3.2.2: the six `assets *-state-store` commands get 404/405, because that API only exists from 3.3. The tests would need version-gating for a 3.2 cell. > * All three: the `xcom` and `dagrun delete` steps after `dags trigger` are flaky. The test writes an XCom before the task starts, and the task clears its XComs when it starts. This is not version related. > > I will open PRs fixing these problems soon! Hope we can get airflowctl released shortly. > > cc [@shahar1](https://github.com/shahar1) Thanks! It would be great :) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
