mozilla-services / mozilla-services/updatebot
Repeat HTTP 500 errors when checking upstream repos
Open
Nobody has claimed this yet.
Bug
P2
- Dominant language
- Python
- Stars
- 9
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
Sentry Issue: UPDATEBOT-PROD-3C
CalledProcessError: Command '['./mach', 'vendor', '--check-for-update', 'js/src/irregexp/moz.yaml']' returned non-zero exit status 1.
(3 additional frame(s) were not displayed)
...
File "components/utilities.py", line 161, in wrapper
return func(*args, **call_kwargs)
File "components/mach_vendor.py", line 26, in check_for_update
result = self.run(["./mach", "vendor", "--check-for-update", library.yaml_path]).stdout.decode().strip()
File "components/commandprovider.py", line 24, in run
return _run(args, shell=shell, clean_return=clean_return,
File "components/commandrunner.py", line 86, in _run
ret.check_returncode()
File "subprocess.py", line 502, in check_returncode
raise CalledProcessError(self.returncode, self.args, self.stdout,
Contributor 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.
Research direction
Start by reproducing the reported command: ./mach vendor --check-for-update js/src/irregexp/moz.yaml. Trace the call through components/mach_vendor.py, components/commandprovider.py, components/commandrunner.py, and components/utilities.py, using the Sentry details to investigate the repeated HTTP 500 failure. Done means the upstream check no longer produces the reported repeated failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100