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

Fix same resource file published more than once #13195

Merged
merged 1 commit into from
Dec 27, 2024

Conversation

bep
Copy link
Member

@bep bep commented Dec 26, 2024

This may still happen, though, in low memory situations or very big sites, but I'm not sure it's worth spending time on fixing that. Writing the same file more than once isn't harmful, the negative effect is the false path warning. We may find a way to detect that situtation if this becomes a real problem.

Fixes #13164

@bep bep force-pushed the fix/resourceonce-13164 branch from c4d94bb to 515d275 Compare December 26, 2024 16:20
This may still happen, though, in low memory situations or very big sites, but I'm not sure it's worth spending time on fixing that. Writing the same file more than once isn't harmful, the negative effect is the false path warning.
 We may find a way to detect that situation if this becomes a real problem.

Fixes gohugoio#13164
@bep bep force-pushed the fix/resourceonce-13164 branch from 515d275 to 0bfd2fd Compare December 26, 2024 17:25
@bep bep merged commit 77824d7 into gohugoio:master Dec 27, 2024
6 checks passed
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.

False path warning / resources possibly written twice to /public in some cases
1 participant