mozilla / mozilla/bugbot

Support running scripts without a people.json

Open
#887 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
68
Forks
92
Avg merge
2d 2h
Merged PRs (30d)
16

Description

E.g. if I run the spambug model:

2020-02-05 12:07:52,126 - INFO - Run tool spambug.py
Traceback (most recent call last):
  File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/home/marco/Documenti/workspace/relman-auto-nag/auto_nag/scripts/spambug.py", line 95, in <module>
    SpamBug().run()
  File "/home/marco/Documenti/workspace/relman-auto-nag/auto_nag/scripts/spambug.py", line 14, in __init__
    self.people = people.People.get_instance()
  File "/home/marco/Documenti/workspace/relman-auto-nag/auto_nag/people.py", line 58, in get_instance
    People._instance = People()
  File "/home/marco/Documenti/workspace/relman-auto-nag/auto_nag/people.py", line 37, in __init__
    with open("./auto_nag/scripts/configs/people.json", "r") as In:
FileNotFoundError: [Errno 2] No such file or directory: './auto_nag/scripts/configs/people.json'

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 by reproducing the spambug run and reading auto_nag/scripts/spambug.py together with auto_nag/people.py, especially People initialization and its people.json access. Trace which scripts require the people data, then verify that scripts that do not need it run successfully when auto_nag/scripts/configs/people.json is absent.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
tooling
Issue type
Feature
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.