You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, usually when checking a very large number of files with many worker threads, you can get weird outputs like this:
...
P 1234:1234 5678:5678 foo/bar/file1.mp3
P 1234:1234 5678:5678 foo/bar/file3.mp3
P 1234:1234 5678:5678 foo/bar/file4.mp3
P 1234:1234 5678:5678
P 1234:1234 5678:5678 foo/bar/file5.mp3
foo/bar/file2.mp3
...
The extraneous new-line and the split-apart result for file2.mp3 are apparently the result of output-buffering issues. I think just flushing after each result should fix it. The logger should support this
The text was updated successfully, but these errors were encountered:
Sometimes, usually when checking a very large number of files with many worker threads, you can get weird outputs like this:
The extraneous new-line and the split-apart result for
file2.mp3
are apparently the result of output-buffering issues. I think just flushing after each result should fix it. The logger should support thisThe text was updated successfully, but these errors were encountered: