MozillaSecurity / MozillaSecurity/fuzzfetch

KeyError: 'crashreporter'

Open
#164 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
48
Forks
12
PR merge metrics
No merged PRs in 30d

Description

Seen on a recent bugmon instance.

Traceback (most recent call last):
  File "C:\Users\task_175351735394693\msys64\opt\python\lib\runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\task_175351735394693\msys64\opt\python\lib\runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "C:\Users\task_175351735394693\msys64\opt\python\Scripts\bugmon-process.exe\__main__.py", line 7, in <module>
  File "C:\Users\task_175351735394693\msys64\opt\python\lib\site-packages\bugmon_tc\process\cli.py", line 125, in main
    process_bug(
  File "C:\Users\task_175351735394693\msys64\opt\python\lib\site-packages\bugmon_tc\process\cli.py", line 48, in process_bug
    bugmon.process(force_confirm)
  File "C:\Users\task_175351735394693\msys64\opt\python\lib\site-packages\bugmon\bugmon.py", line 638, in process
    self._confirm_open()
  File "C:\Users\task_175351735394693\msys64\opt\python\lib\site-packages\bugmon\bugmon.py", line 196, in _confirm_open
    orig = self._reproduce_bug(config, self.bug.branch, bid)
  File "C:\Users\task_175351735394693\msys64\opt\python\lib\site-packages\bugmon\bugmon.py", line 421, in _reproduce_bug
    build = Fetcher(
  File "C:\Users\task_175351735394693\msys64\opt\python\lib\site-packages\fuzzfetch\core.py", line 177, in __init__
    self.resolve_targets(self._targets)
  File "C:\Users\task_175351735394693\msys64\opt\python\lib\site-packages\fuzzfetch\core.py", line 359, in resolve_targets
    syms_wanted = bool(self.moz_info["crashreporter"])
KeyError: 'crashreporter'

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with fuzzfetch/core.py at resolve_targets(), specifically the access to moz_info["crashreporter"] shown in the traceback. Reproduce the bug with the reported bugmon scenario, then verify that target resolution no longer raises KeyError when that metadata is absent.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.