ENG-4867 Ensure closing of file stream after each component build #166
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…cess Resolves an issue where a locked file stream after the initial build processes when running the pack command causes problems with the subsequent (using podman) process. The file is now manually closed with after each initial build process finishes.
zonia3000
approved these changes
May 24, 2023
|
Requested publication of version |
|
Requested publication of version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Resolves an issue where a locked file stream after the initial build processes when running the pack command causes problems with the subsequent
docker build(using podman) process. The file stream is now manually closed withend()after each initial build process finishes.