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
We were considering that a chunk A contains a chunk B if chunk B start
after chunk A and ends before or on the same offset than chunk A.
This caused issues with compressed DMG images where two handlers would
rightfully identify two chunks:
- a bzip chunk starting at offset 0 and ending before the DMG plist
- a DMG chunk starting at offset 0 and ending after the DMG footer
We therefore adapted our definition of contains() where a contained
chunk can start at the same offset but ends before, or start after the
containing chunk but can end on the same offset.
0 commit comments