fix(cdk-assets): asset concurrency leaves a corrupted archive #24026
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.
This is a re-roll of #23677 which was reverted in #23994 because the
randomUUID()
function from the original solution was not available in Node versions below 14.17 (and we advertise compatibility with Node 14.*).We didn't actually need a UUID, just any random string, so replace it with a function that generates a random string in a different way.
Resolves #23290
A very simple fix for the issue where builds with
--concurrency
specified can lead to corrupt archives. Rather than use the outputFile as the basis for the temp file name we simply use a random string.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license