lzma: stream padding in xz files
Open
Nobody has claimed this yet.
3.10
3.11
3.7 (EOL)
3.8 (EOL)
3.9 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 44134 |
|---|---|
| Nosy | @animalize, @rogdham |
| Files |
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 2021-05-14.17:52:02.842>
labels = ['type-bug', '3.8', '3.9', '3.10', '3.11', '3.7', 'library']
title = 'lzma: stream padding in xz files'
updated_at = <Date 2021-05-16.10:27:53.156>
user = 'https://github.com/rogdham'
bugs.python.org fields:
activity = <Date 2021-05-16.10:27:53.156>
actor = 'rogdham'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2021-05-14.17:52:02.842>
creator = 'rogdham'
dependencies = []
files = ['50044', '50045']
hgrepos = []
issue_num = 44134
keywords = []
message_count = 2.0
messages = ['393681', '393738']
nosy_count = 3.0
nosy_names = ['nadeem.vawda', 'malin', 'rogdham']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue44134'
versions = ['Python 3.6', 'Python 3.7', 'Python 3.8', 'Python 3.9', 'Python 3.10', 'Python 3.11']
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
The issue provides example1.xz and example2.xz as reproduction inputs; start by reproducing the behavior with Python's lzma support and locating the existing lzma tests. Confirm the expected handling of stream padding and add coverage for both examples, but the migrated issue does not identify a source file or precise expected result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100