Skip to content

bpo-12800: 'tarfile.StreamError: seeking backwards is not allowed' when extract symlink #20972

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

Closed
wants to merge 3 commits into from

Conversation

catlee
Copy link

@catlee catlee commented Jun 18, 2020

This is addressing the review comments in #13217

https://bugs.python.org/issue12800

websurfer5 and others added 3 commits June 18, 2020 18:07
module in stream mode ('r|') fails with an exception when a file
or symlink of the same name already exists. The fix is to remove
the existing file or symlink before extraction. Tests are included.
@the-knights-who-say-ni
Copy link

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept this contribution by verifying everyone involved has signed the PSF contributor agreement (CLA).

CLA Missing

Our records indicate the following people have not signed the CLA:

@catlee

For legal reasons we need all the people listed to sign the CLA before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

If you have recently signed the CLA, please wait at least one business day
before our records are updated.

You can check yourself to see if the CLA has been received.

Thanks again for the contribution, we look forward to reviewing it!

@JulienPalard
Copy link
Member

JulienPalard commented Jul 9, 2020

I'm not a fan of using open to create a file, what about using pathlib?

Also why tar.extractall(path=support.SAVEDCWD)? It will extract to the cpython root, out of the temporary directory, so it won't get cleaned afterwards.

For readability maybe rename source to regular_file, and link to symlink.

@JulienPalard
Copy link
Member

Oh, @catlee, took more time to look at it, I started suspecting strange thing while spotting the exact same test already existing in the file. See my comment in bpo.

I opened a much simpler PR #21409 restoring the original test instead of writing new ones.

@taleinat
Copy link
Contributor

Good catch @JulienPalard!

Thanks for the PR, @catlee, but I'm closing this in favor of PR GH-21409.

@taleinat taleinat closed this Sep 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants