Skip to content
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

compressed_file_reader file archive mechanism does not always work #17

Open
macgyver603 opened this issue Feb 7, 2019 · 1 comment
Open

Comments

@macgyver603
Copy link
Contributor

The slicer doesn't guarantee slice order, so relying on seeing this attribute on a slice does not necessarily mean the whole file has been processed.

@macgyver603
Copy link
Contributor Author

To clarify, this mechanism only moves a "completed" file to an archive directory instead of recompressing it, so the fix will be to just leave the uncompressed file as-is after processing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant