Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Made usage of Path explicit for Edge Worker pid files #43308

Conversation

OliverWannenwetsch
Copy link
Contributor

Summary

This PR fixes a type confusion in the pid file path in the Edge worker.
Now, pid_file_path is explicitly treated as string in the entire implementation of the Edge Worker cli, which interfaces with the lib lockfile.pidlockfile for pid file interaction, consuming file path as string only

Changes in Detail

  • updated function _write_pid_to_pidfile to consume pid file path as string (as any other function in the module edge_command
  • converted property pid_file_path of class _EdgeWorkerClifrom Path to str

@OliverWannenwetsch OliverWannenwetsch force-pushed the bugfix/321279-edge-worker-pid-file-not-handled-as-path-type branch from b31c5e5 to 41e64ca Compare October 23, 2024 12:58
@jscheffl jscheffl merged commit 3b0cb76 into apache:main Oct 23, 2024
56 checks passed
harjeevanmaan pushed a commit to harjeevanmaan/airflow that referenced this pull request Oct 23, 2024
* Made usage of Path explicit for Edge Worker pid files

* Updated version number of Edge Worker provider package

* Fixed pytests by findings of mypy
PaulKobow7536 pushed a commit to PaulKobow7536/airflow that referenced this pull request Oct 24, 2024
* Made usage of Path explicit for Edge Worker pid files

* Updated version number of Edge Worker provider package

* Fixed pytests by findings of mypy
ellisms pushed a commit to ellisms/airflow that referenced this pull request Nov 13, 2024
* Made usage of Path explicit for Edge Worker pid files

* Updated version number of Edge Worker provider package

* Fixed pytests by findings of mypy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants