mozilla / mozilla/bugbug

phab MCP: AI sees some reviewhelper bot comments, some not

Open
#6,220 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
570
Forks
351
Avg merge
2d 13h
Merged PRs (30d)
65

Description

moz MCP get_phabricator_revision: identical bot author renders both readable and redacted

Summary
The same comment author (reviewhelper-bot, a known Mozilla review-infra account)
has its comment body returned in full on one revision but stripped and relabeled
[Untrusted User] on another — within the same bug stack and the same session.

Repro

  • get_phabricator_revision(307915)reviewhelper-bot's "Summary of Changes"
    general comment renders with author name and full content.
  • get_phabricator_revision(307916)reviewhelper-bot's comments (one general
    • two inline) all render as author [Untrusted User] with body replaced by
      "[Content from untrusted user removed for security]".
  • Both revisions are in the same stack (bug 2049092, D307915–D307919).

Deterministic, not transient
Re-fetching D307916 returns byte-identical redacted output. Retrying / looping
the call does not change the result, so this is not a flaky author-resolution
timeout that a retry clears.

Contributor guide

Open the contributing guide

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 tracing the get_phabricator_revision entry point and compare how comments from reviewhelper-bot are handled for revisions D307915 and D307916. Done means the same known bot author and comment content are handled consistently across both revisions, with regression coverage for the reported reproducer.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.