Closed jtmoon79 closed 2 months ago
My guess is the "zero block stage" which has special processing for ad-hoc logs without a year, also proactively dropped old blocks. Then during the later "streaming stage", the request for block 0 failed. That block was already dropped leading to read_block_FileGz
returning Done
.
This should have been caught by compare-current-and-expected/compare.sh
.
This may not be related to being a compressed file. Just noticed an error with datetime matching
$ ./target/release/s4 -u -s ./logs/other/tests/gen-20-2-2-faces.log
19700101T070001.000+0000:01 😀😁😂😃😄😅😆😇😈😉😊😋😌😍😎😏😐😑😒😓😔😕😖😗😘😙😚😛😜😝😞😟😠😡😢😣😤😥😦😧😨😩😪😫😬😭😮😯😰😱😲😳😴😵😶😷😸😹😺😻😼😽😾😿🙀🙁🙂🙃
...
The 01
is interpreted as 1970-01-01T07:00:01.
Describe the bug
A gzipped file with datetime pattern without a year, e.g.
Mar 21 23:33:53 fink NetworkManager[755]: <info>
, prints the first few lines then quits.To Reproduce
Given file like
kern.log.2.gz
found on a Ubuntu 16 systemThis file is 306282 bytes decompressed according to
gzip -vdck /var/log/kern.log.2.gz | wc -c
s4
only prints the first three lines and then stops processing.Debug build has these interesting messages:
Environment:
Other
Looking at debug output, this appears to be a result of #283