Fix #9358: TarScanner no longer ignores empty files #9367
Merged
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.
Motivation / Problem
An AI requires a file with 0 bytes to be able to start, but the tar scanner skips empty files, causing the AI to fail with a "file not found" error.
See #9358
Description
The problem is solved by allowing tar scanner to add empty files.
Limitations
It was suggested to fix it this way, but there's some uncertainty about it. I'm not familiar with this code.
Checklist for review
Some things are not automated, and forgotten often. This list is a reminder for the reviewers.