Skip to content

Fix false positive writability check on cache directory #23049

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

Merged
merged 1 commit into from
Dec 4, 2024

Conversation

sbc100
Copy link
Collaborator

@sbc100 sbc100 commented Dec 2, 2024

We were incorrectly reporting non-existent parent directories as non-writable.

This was broken in #22801.

@sbc100 sbc100 requested a review from kripken December 2, 2024 21:11
@sbc100 sbc100 force-pushed the em_cache branch 2 times, most recently from 8704530 to 7c65e19 Compare December 2, 2024 21:12
@sbc100 sbc100 enabled auto-merge (squash) December 3, 2024 00:27
@sbc100 sbc100 force-pushed the em_cache branch 3 times, most recently from b1013d1 to 32b3595 Compare December 3, 2024 04:41
We were incorrectly reporting non-existent parent directories as
non-writable.

This was broken in emscripten-core#22801.
@sbc100 sbc100 disabled auto-merge December 4, 2024 04:53
@sbc100 sbc100 merged commit 58889f9 into emscripten-core:main Dec 4, 2024
26 of 28 checks passed
@sbc100 sbc100 deleted the em_cache branch December 4, 2024 04:53
hedwigz pushed a commit to hedwigz/emscripten that referenced this pull request Dec 18, 2024
…ore#23049)

We were incorrectly reporting non-existent parent directories as
non-writable.

This was broken in emscripten-core#22801.
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.

2 participants