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

Add a thread-safe implementation of Process.currentDirectoryURL #4981

Merged
merged 1 commit into from
Sep 26, 2024

Conversation

jakepetroules
Copy link
Contributor

posix_spawn_file_actions_addchdir_np is the official way to set the working directory of a spawned process and is supported on both macOS and glibc (Linux, etc.). This makes Process.currentDirectoryURL thread-safe, as the current approach will result in the working directory being nondeterministically assigned when spawning processes across multiple threads, using different working directories.

@jakepetroules
Copy link
Contributor Author

@swift-ci please test

@jakepetroules
Copy link
Contributor Author

@swift-ci please test

@parkera
Copy link
Contributor

parkera commented Sep 9, 2024

@iCharlesHu can you review please?

@jakepetroules
Copy link
Contributor Author

@swift-ci please test

@jakepetroules
Copy link
Contributor Author

@swift-ci test windows

posix_spawn_file_actions_addchdir_np is the official way to set the working directory of a spawned process and is supported on both macOS and glibc (Linux, etc.). This makes Process.currentDirectoryURL thread-safe, as the current approach will result in the working directory being nondeterministically assigned when spawning processes across multiple threads, using different working directories.
@jakepetroules
Copy link
Contributor Author

@swift-ci please test

@jakepetroules jakepetroules merged commit 4a86531 into main Sep 26, 2024
2 of 3 checks passed
@jakepetroules jakepetroules deleted the process-currentdir-threadsafe branch September 26, 2024 08:17
jakepetroules added a commit that referenced this pull request Sep 28, 2024
Swift still needs to support Amazon Linux 2 until it EoLs in mid-2025. So restore the thread-unsafe fallback for systems with glibc older than version 2.29, which was removed in #4981.
jakepetroules added a commit that referenced this pull request Sep 29, 2024
Swift still needs to support Amazon Linux 2 until it EoLs in mid-2025. So restore the thread-unsafe fallback for systems with glibc older than version 2.29, which was removed in #4981.
jakepetroules added a commit that referenced this pull request Sep 30, 2024
Swift still needs to support Amazon Linux 2 until it EoLs in mid-2025. So restore the thread-unsafe fallback for systems with glibc older than version 2.29, which was removed in #4981.
jakepetroules added a commit that referenced this pull request Oct 2, 2024
Swift still needs to support Amazon Linux 2 until it EoLs in mid-2025. So restore the thread-unsafe fallback for systems with glibc older than version 2.29, which was removed in #4981.
jakepetroules added a commit that referenced this pull request Oct 2, 2024
Swift still needs to support Amazon Linux 2 until it EoLs in mid-2025. So restore the thread-unsafe fallback for systems with glibc older than version 2.29, which was removed in #4981.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants