-
Notifications
You must be signed in to change notification settings - Fork 20
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
runtime error: index out of range [0] with length 0 #112
Comments
If you can provide (a link to) an archive that triggers this bug that would be helpful otherwise I'm a bit restricted. |
Fair enough! I've actually had hard time reproducing this specific issue because I've been hitting another edge case, and that one seems more reliably reproducible. I'll share that today. |
I'm guessing it's something related to the CRC digests being optional, but an example archive would confirm that, and also if it's small enough, it becomes part of the test suite to ensure I don't inadvertently break it again. |
I'm running into the same issue, but I don't have access to the archive thats causing it. I'll keep working at a repro. |
I've managed to narrow the failure down to a handful of repositories, I just need to figure out the specific repository and file. Hopefully I'll be able to share a reproducer soon. |
Awesome. That's erroring nicely, (in a good way!), and it's small enough I can add it as a new test case. Running |
@rgmz @bill-rich can you try the branch in #143 and see if that fully fixes things? It passes now on the linked archive. |
That seems to work. I'll let you know if I encounter any issues. Thanks again, @bodgit! |
While processing a large amount of files, I encountered the following panic.
The issue appears to be caused by attempting to access the first (0) value of
h.streamsInfo.subStreamsInfo.digest
when it is empty. I don't know what the specific culprit was at the moment, but I'm sharing this now in case the issue/solution is obvious.sevenzip/types.go
Line 825 in 8185d4f
sevenzip/types.go
Lines 832 to 833 in 8185d4f
The text was updated successfully, but these errors were encountered: