tggm803sc commented on PR #77077: URL: https://github.com/apache/airflow/pull/77077#issuecomment-6876756528
CI is green on `bb44bff` — [run 43561404881](https://github.com/apache/airflow/actions/runs/43561404881): | check | result | | --- | --- | | `CI image checks / Static checks` | pass | | `CI image checks / Build documentation` | pass | | `CI image checks / Publish documentation and validate versions` | pass | | `CI passed` | pass | Two things had to be fixed after the first push, both visible in the commit history: - The new page was not referenced from any toctree, so the docs build reported it as an orphan. It is now listed in `airflow-core/docs/howto/index.rst` next to the existing `docker-compose/index` guide. - The ASF header in `local-executor.rst` was missing the `..` comment markers on the license-URL line and the "Unless required by applicable law" line. `insert-license` only recognises the header in its canonical form, so it treated the file as carrying an inconsistent license, prepended a TODO and failed `Static checks`. The header now matches `scripts/ci/license-templates/LICENSE.rst` exactly. One gap remains: **the containers have never been started.** The machine I had access to has no Docker daemon, so `docker compose up`, the `airflow`/`airflow` login and a task actually executing under LocalExecutor are unverified. Everything tested so far is static validation of the compose file plus the docs build. The end-to-end path should be treated as untested until someone runs it on a Docker host with at least 4 GB — happy to do that myself if that run would be useful, otherwise it is a gap reviewers should know about. The Testing section of the description says the same. The PR is still in draft; I have not been able to flip it to ready from here. -- 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]
