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

Use hardlinking when possible for mypy cache (Cherry-pick of #19633) #19649

Merged
merged 1 commit into from Aug 22, 2023

Conversation

WorkerPants
Copy link
Member

As surfaced by @jsirois in #19610 (comment), as a way of making the mypy cache "atomic" in all scenarios, we'll attempt a hardlink and fall back to copying/moving.

As surfaced by @jsirois in
#19610 (comment),
as a way of making the mypy cache "atomic" in all scenarios, we'll
attempt a hardlink and fall back to copying/moving.
@WorkerPants WorkerPants added this to the 2.16.x milestone Aug 22, 2023
@WorkerPants WorkerPants added the category:bugfix Bug fixes for released features label Aug 22, 2023
@huonw huonw merged commit 3b9f5ae into 2.16.x Aug 22, 2023
24 checks passed
@huonw huonw deleted the cherry-pick-19633-to-2.16.x branch August 22, 2023 23:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:bugfix Bug fixes for released features
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants