Exception when parsing emails: 'tuple' object has no attribute 'patch'
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start in patchwork/bin/parsemail.py at parse_mail around line 714, then trace how content is produced before content.patch is accessed. Reproduce the failure with an affected email or patch and determine why content is a tuple; done means those emails parse without the AttributeError.
Written by the indexing model from the issue text.
Description
That's the traceback I have on some of the patches on fdo:
Traceback (most recent call last):
File "/srv/patchwork.freedesktop.org/patchwork/bin/parsemail.py", line 826, in main
return parse_mail(mail)
File "/srv/patchwork.freedesktop.org/patchwork/bin/parsemail.py", line 714, in parse_mail
patch = content.patch
AttributeError: 'tuple' object has no attribute 'patch'
- Dominant language
- Python
- Stars
- 22
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from dlespiau/patchwork
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in dlespiau/patchwork
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100