Use unique tmp file names to avoid race conditions #1119
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When multiple concurrent processes read the same S3 file (or HTTP URL), they would all use the same deterministic temporary filename based on the S3 object hash (or HTTP URL). This caused race conditions where one process could delete the temp file after reading it while another was still trying to read it, resulting in "No such file or directory" errors.
See below for a script to reproduce.
Solution
Modified
Explorer.PolarsBackend.Shared.build_path_for_entry/1to append a random suffix to the temporary filename, ensuring each download gets a unique path.Problem reproduce script