potiuk opened a new pull request #18464: URL: https://github.com/apache/airflow/pull/18464
In some cases files created inside the container on linux in sources are owned by root - so far we cleaned only some directories that we knew were touched by Airflow, but in case of branch switching some folders/files might also got created as owned by root. This PR adds AIRFLOW_SOURCES and "dags" folders to the list of folders to fix ownership of. This might lead to slightly longer exit time when exiting from Breeze, but since we are running it only when the host is Linux and the fixung is rather performant - with explicitly finding files and dirs owned by root, this should not be a problem. It would be much bigger problem on MacOS,Windows due to slow filesystem, but on MacOS it is not needed as there ownership mapping is done using the filesystem itself. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md). -- 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]
