[copy_duplicate_info] KeyError: 'bug_count'
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start with copy_duplicate_info.py at get_bugs and trace into bugbot/bzcleaner.py, especially get_bugs, get_email_data, and send_email at the locations in the traceback. Reproduce the copy_duplicate_info rule's run path and inspect where the expected bug_count data is accessed. Done means the rule completes without the reported KeyError.
Written by the indexing model from the issue text.
Description
Sentry Issue: BUGBOT-17
KeyError: 'bug_count'
(3 additional frame(s) were not displayed)
...
File "bugbot/bzcleaner.py", line 858, in run
self.send_email(date=date)
File "bugbot/bzcleaner.py", line 771, in send_email
data = self.get_email_data(date)
File "bugbot/bzcleaner.py", line 689, in get_email_data
bugs = self.get_bugs(date=date)
File "copy_duplicate_info.py", line 99, in get_bugs
bugs = super(CopyDuplicateInfo, self).get_bugs(date=date, bug_ids=bug_ids)
File "bugbot/bzcleaner.py", line 464, in get_bugs
).get_data().wait()
Rule copy_duplicate_info
- Dominant language
- Python
- Stars
- 69
- Forks
- 93
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 20
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from mozilla/bugbot
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 4 days
-
AttributeError: 'list' object has no attribute 'values'Possibly taken @SAY-5 claimed this 40 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 4 days
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 4 days
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
mozilla/bugbot#3010 · 1 comment ·
Maintainers usually reply within 4 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
FuRongJun-1999/dsh-memory#56 ·
Maintainers usually reply within 1 day
-
Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pgadmin-org/pgadmin4#10503 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
521xueweihan/HelloGitHub#3857 ·
-
needs-ac
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Ikalus1988/MisakaNet#2845 ·
Maintainers usually reply within 1 day
-
bug connectors operations
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyinfra-dev/pyinfra#1989 ·
Maintainers usually reply within 3 days