-
Notifications
You must be signed in to change notification settings - Fork 314
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
Downloader: Skip zero size artifacts #8116
Comments
How would a user become aware of these errors in order to fix them if ORT would "gracefully ignore those files"? Or do you mean that an error should be logged, but no exception should be thrown? But actually, I've not seen this before myself, so I'm not sure how worthwhile a special handling for 0-byte files would be. |
This can be shown as an issue, but the scan should continue. |
Most likely the root cause was an issue with osgeo repository (repo.osgeo.org) which happened last year. Discussion: https://www.mail-archive.com/[email protected]/msg20339.html |
I've also just came across this. What surprises me, is that the logs look as if the exception is not caught. See: ort/scanner/src/main/kotlin/Scanner.kt Lines 705 to 719 in bf5661b
|
I guess #8303 helps? |
@timo-HERE could you please check whether the issue is resolved for you with the latest |
Gradle artifacts are archive files. A file with zero bytes size never is a valid archive, so fallback to `RemoteArtifact.EMPTY` in that case. This fixes one possible rot cause of #8116. Signed-off-by: Frank Viernau <[email protected]>
Maven artifacts are archive files. A file with zero bytes size never is a valid archive, so fallback to `RemoteArtifact.EMPTY` in that case. This fixes one possible root cause of #8116. Signed-off-by: Frank Viernau <[email protected]>
Maven artifacts are archive files. A file with zero bytes size never is a valid archive, so fallback to `RemoteArtifact.EMPTY` in that case. This fixes one possible root cause of #8116. Signed-off-by: Frank Viernau <[email protected]>
Feel free to reopen if the issue persists. |
Sometimes ORT comes across with zero size source artifacts. Those obviously are errors that should be fixed/deleted from the repository, but I think ORT also should gracefully ignore those files instead of trying to unpack 0 byte files.
The text was updated successfully, but these errors were encountered: