fix: Fails to extract file which might or might not be malformed (#376)#426
fix: Fails to extract file which might or might not be malformed (#376)#426Pr0methean merged 10 commits intomasterfrom
Conversation
|
Resolves #376 |
|
To provide feedback, I recommend leaving inline comments for best results. Navigate to the Files changed tab and leave comments on the proposed code changes. Choose Start review for each comment, and then choose Request changes, and I'll propose revised changes. If creating PR-level comments, include as much detail as possible in your feedback (for example, file name, class name, line number). |
|
The tests are failing in CI with |
|
Update: the cause of most of these failures is that |
41ff300 to
62353ca
Compare
|
Update: one new test is still failing on Unix because a Windows drive letter is being interpreted as a normal directory on Unix. Apparently Rust's |
|
I think this MR introduced the file https://github.com/zip-rs/zip2/blob/master/test_fix.rs I think we should delete it |
|
That file was added by Amazon Q Developer to the first version of this PR back in September: 18b8948 I'll take another look in the morning, but I suspect that Q added this test for a good reason, given how lazy it was in general at that time, and that if we deleted it without merging it into the existing tests then we'd get a coverage regression. |
The problem is that it's not even a test :( but just a
Thanks |
Fair enough; I'll convert it into a test if no existing test uses absolute paths (and I don't remember there being any that do). |
Pull request for Fails to extract file which might or might not be malformed