tarfile.TarFile may write corrupt files if not closed
Open
Nobody has claimed this yet.
3.7 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 34662 |
|---|---|
| Nosy | @gustaebel, @lordmauve |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2018-09-13.17:20:55.522>
labels = ['3.7', 'type-bug', 'library']
title = 'tarfile.TarFile may write corrupt files if not closed'
updated_at = <Date 2018-09-13.21:47:05.383>
user = 'https://github.com/lordmauve'
bugs.python.org fields:
activity = <Date 2018-09-13.21:47:05.383>
actor = 'ned.deily'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2018-09-13.17:20:55.522>
creator = 'lordmauve'
dependencies = []
files = []
hgrepos = []
issue_num = 34662
keywords = []
message_count = 2.0
messages = ['325266', '325269']
nosy_count = 2.0
nosy_names = ['lars.gustaebel', 'lordmauve']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue34662'
versions = ['Python 3.7']
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the tarfile.TarFile implementation and reproduce the reported corruption when a writable archive is not closed. No source file, test, or reproduction steps are named in the issue, so identify the relevant archive-finalization behavior and add coverage showing what should happen for an unclosed TarFile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100