This repository has been archived by the owner on Jan 6, 2022. It is now read-only.
Use print(flush=True) to log scan progress #379
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.
When looking at logs of a scan container with
kubectl logs
or in ELK, nothing is actually printed until the entire scan is done. I believe this is because block buffering is being used and not enough data is printed for force a write. Instead, let's force a flush after each line. We don't have to call.write()
for this; we can just useprint()
.