[PR #24] Temporary fix for solid archive detection until SharpCompress makes another release. #52

Open
opened 2026-01-29 21:16:47 +00:00 by claunia · 0 comments
Owner

Original Pull Request: https://github.com/SabreTools/SabreTools.Serialization/pull/24

State: closed
Merged: Yes


At present, the release of SharpCompress that Serialization uses is missing the fix for single-block solid archive detection that was pushed a month or so afterwards https://github.com/adamhathcock/sharpcompress/pull/924 . From my own observations, and the experiences of various MPF/BOS users, solid archives (especially solid 7Z archives) tend to only be one block, so this winds up being a pretty major issue, resulting in extraction more or less locking up anytime a 7z is encountered. I understand that this fix isn't the most elegant, but it doesn't actually waste that much time since it only needs to check for two file entries, and it will have a major positive impact on processing times, given the state of solid extraction without it is borderline unusable on large archives with many files.
This backports what I had done for the original commit ecd99b157d in the pull where this was first found https://github.com/SabreTools/BinaryObjectScanner/pull/375 .

**Original Pull Request:** https://github.com/SabreTools/SabreTools.Serialization/pull/24 **State:** closed **Merged:** Yes --- At present, the release of SharpCompress that Serialization uses is missing the fix for single-block solid archive detection that was pushed a month or so afterwards https://github.com/adamhathcock/sharpcompress/pull/924 . From my own observations, and the experiences of various MPF/BOS users, solid archives (especially solid 7Z archives) tend to only be one block, so this winds up being a pretty major issue, resulting in extraction more or less locking up anytime a 7z is encountered. I understand that this fix isn't the most elegant, but it doesn't actually waste that much time since it only needs to check for two file entries, and it will have a major positive impact on processing times, given the state of solid extraction without it is borderline unusable on large archives with many files. This backports what I had done for the original commit https://github.com/SabreTools/BinaryObjectScanner/pull/375/commits/ecd99b157db50c34cd0c91fa36ffde9f9c9b10e3 in the pull where this was first found https://github.com/SabreTools/BinaryObjectScanner/pull/375 .
claunia added the pull-request label 2026-01-29 21:16:47 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SabreTools/SabreTools.Serialization#52