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
I got that error at one of the executions while processing a 540 image set.
Don't know if it's really a bug, or some problem with filesystem or temp directory...
0.4.2
Processing 540 time slices
████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 185/540 thread 'main' panicked at 'called Result::unwrap()on anErr value: Custom { kind: InvalidInput, error: "corrupt gzip stream does not have a matching checksum" }', src/streams.rs:188:28
The text was updated successfully, but these errors were encountered:
At first glance, I have no idea what that could be.
You did not have another instance of the tool running? That would cause problems if both instances used the same temp directory (might be necessary to find a solution for this case anyway).
Are you able to reproduce this error? I.e. does it happen again under the same settings?
Also, could you give the command you used? Did you use option --slice?
Thanks again!
EDIT: In case multiple instances were the cause of the problem, that should be solved now on version 0.6.2
mlange-42
changed the title
Possible little bug?
Error reading time slices: "corrupt gzip stream does not have a matching checksum"
Apr 20, 2020
mlange-42
changed the title
Error reading time slices: "corrupt gzip stream does not have a matching checksum"
[Bug] Error reading time slices: "corrupt gzip stream does not have a matching checksum"
Apr 20, 2020
I got that error at one of the executions while processing a 540 image set.
Don't know if it's really a bug, or some problem with filesystem or temp directory...
0.4.2
Processing 540 time slices
████████████████████████░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ 185/540
thread 'main' panicked at 'called
Result::unwrap()on an
Errvalue: Custom { kind: InvalidInput, error: "corrupt gzip stream does not have a matching checksum" }', src/streams.rs:188:28
The text was updated successfully, but these errors were encountered: