TypeError: Parser must be a string or character stream, not NoneType
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 68
- Forks
- 92
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 16
Description
Sentry Issue: BUGBOT-52
TypeError: Parser must be a string or character stream, not NoneType
(17 additional frame(s) were not displayed)
...
File "bugbot/bzcleaner.py", line 712, in get_email_data
bugs = self.get_bugs(date=date)
File "patch_closed_bug.py", line 44, in get_bugs
bugs = super().get_bugs(date, bug_ids, chunk_size)
File "bugbot/bzcleaner.py", line 486, in get_bugs
).get_data().wait()
File "bugbot/bzcleaner.py", line 362, in bughandler
if self.handle_bug(bug, data) is None:
File "patch_closed_bug.py", line 67, in handle_bug
resolved_at = parser.parse(bug["cf_last_resolved"])
Rule patch_closed_bug
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.
Research direction
Read patch_closed_bug.py at handle_bug (line 67) and trace how cf_last_resolved reaches parser.parse through bugbot/bzcleaner.py. Reproduce the case where that value is None, then verify the patch_closed_bug rule handles it without raising the reported TypeError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100