Set fuzzer author as reporter for bugs from external fuzzers by jr2bg · Pull Request #5312 · google/clusterfuzz

jr2bg · 2026-06-04T14:11:48Z

Changes:

Added primary_owner field to Fuzzer model in data_types.py.
Added "Primary owner" input field to the fuzzer edit form in edit-form.html.
Updated fuzzers.py handler to save the primary_owner field.
Updated file_issue in issue_filer.py to use fuzzer.primary_owner as the reporter if available.
Added unit tests in issue_filer_test.py to verify the new behavior.

Feature tests

Show “owner” textbox

Preconditions

Code already on dev instance

Steps

Enter to https://gosst.development.clusterfuzz.com/fuzzers
Click “CREATE NEW”
Screenshot on the popup, highlighting the “Primary owner (email)” textbox

Evidence

Step 3

Show owner entry on Pantheon Audit Logs

Preconditions

Code already on dev instance

Steps

Enter to https://gosst.development.clusterfuzz.com/fuzzers
Click “CREATE NEW”
Fill the form with the next information
- Name: new_fuzzer_with_owner_jabg
- Select/modify jobs: libfuzzer_chrome_asan
- Owner: jabgonzalez@google.com
- Corpus: None
- Fuzzer archive: ???
- Environment variables: None
- External contribution: True
Click “Submit”
Go to dev logs https://pantheon.corp.google.com/logs/query;cursorTimestamp=2026-04-21T13:41:59.977146Z?e=-13802955&mods=logs_tg_prod&project=clusterfuzz-development and search for the new fuzzer
Take a screenshot of the result, highlighting the “Primary owner (email)” entry
Go to https://gosst.development.clusterfuzz.com/fuzzers
Search the recently created fuzzer new_fuzzer_with_owner_jabg
Take a screenshot

Evidence

Step 6

Step 10

dylanjew

Great job overall!

A couple things:

Change the branch to merge this into master
Please run python butler.py format and python butler.py lint
Could you add a section to your description explaining the steps that you went through to test this? It would be great to include screenshots of this is in dev and then verifying the field in the Datastore. Let me know if you have any questions
Similarly, the backfill script component of this bug probably warrants another section in the PR description. It should cover the order of operations for rolling out this change and how you're going to get the primary owner data for the backfill. Again, lmk if I can help with this. The state of our blackbox fuzzers is not great, and there are many that we need to track down their status/owners.

dylanjew · 2026-07-16T15:59:15Z

+    # Intercept new_issue so we can capture the saved issue object.
+    original_new_issue = issue_tracker.new_issue
+
+    def mock_new_issue():


I'd prefer to mock as little as possible and keep the mocks to the external calls, e.g. the _execute request in test_filed_issue_google_issue_tracker

dylanjew · 2026-07-16T16:05:17Z


-  issue.reporter = user_email
+  if fuzzer and getattr(fuzzer, 'primary_owner', None):
+    issue.reporter = fuzzer.primary_owner


We sometimes use the reporter to determine whether clusterfuzz filed the bug. Is there another place where we are setting metadata of some kind, e.g. a label/hotlist that stays on the bug so that we can continue to track clusterfuzz filed bugs?

- issue_filer.py Get fuzzer from DataStore query, handles cases when no `primary_owner` is found, does not consider yet `external_contribution. - migrate_fuzzer_owners.py Removes the owner

…uzzer-owner

hunsche

Your branch is out of date with the main branch, and the tests are failing. Please update your branch and fix the issues.

Also, how did you test these changes?

dylanjew · 2026-07-28T13:18:59Z

Your branch is out of date with the main branch, and the tests are failing. Please update your branch and fix the issues.

Sorry, the test is failing because I had a bad commit last week during the outage. It should pass once the branch is rebased.

Also, how did you test these changes?

@hunsche, There's a description of how @jr2bg tested the changes with screenshots in the description

dylanjew

@jr2bg is OOO but I rebased the PR

decoNR

I was wondering if changing the reporter has any implications regarding the ClusterFuzz service account losing access to the issue. I imagine that is not the case because ClusterFuzz has a workflow that allows a user to create an issue and link it to a test case, and ClusterFuzz is still able to interact with the issue. I am okay with merging, given that this can only fail for fuzzers where you have set the primary_owner, which are the ones you are monitoring closely and have control over.

I am waiting for comments to be resolved before approving.

Requests were fulfilled.

dylanjew · 2026-08-13T14:50:43Z

I was wondering if changing the reporter has any implications regarding the ClusterFuzz service account losing access to the issue. I imagine that is not the case because ClusterFuzz has a workflow that allows a user to create an issue and link it to a test case, and ClusterFuzz is still able to interact with the issue. I am okay with merging, given that this can only fail for fuzzers where you have set the primary_owner, which are the ones you are monitoring closely and have control over.

Thanks for thinking about this! Totally agree with your conclusion. We're going to separate the actual roll out of this feature from the logic in this PR. I think there are going to be a couple systems that rely on the clusterfuzz service account as the reporter to detect that the bug came from Clusterfuzz.

jr2bg requested a review from dylanjew June 4, 2026 14:11

jr2bg requested a review from a team as a code owner June 4, 2026 14:11

dylanjew reviewed Jun 4, 2026

View reviewed changes

PauloVLB force-pushed the dev branch from a039693 to 4715844 Compare June 8, 2026 17:39

jr2bg changed the base branch from dev to master June 12, 2026 20:03

jr2bg force-pushed the feature/report-by-fuzzer-owner branch 2 times, most recently from 71a3845 to 1c3affd Compare June 15, 2026 18:52

jr2bg force-pushed the feature/report-by-fuzzer-owner branch from 1c3affd to e4b33cd Compare July 16, 2026 13:51

dylanjew reviewed Jul 16, 2026

View reviewed changes

jr2bg force-pushed the feature/report-by-fuzzer-owner branch from e4b33cd to 4eb3238 Compare July 23, 2026 13:35

jr2bg added 8 commits July 23, 2026 17:23

Set fuzzer author as reporter for bugs from external fuzzers

d991c8b

Add license. Modify locations.

f8ad570

Migrate from monorail to buganizer.

62e10a8

Resolve comments on issue filing

4024e3e

- issue_filer.py Get fuzzer from DataStore query, handles cases when no `primary_owner` is found, does not consider yet `external_contribution. - migrate_fuzzer_owners.py Removes the owner

Remove migrate and correct comment

5a498d2

Remove exception and check attribute in fuzzer

751a71e

Restructure mocks for issue filer tests

d85e77a

consider primary owner on tests

5c0f78e

jr2bg force-pushed the feature/report-by-fuzzer-owner branch from 4921ce2 to 5c0f78e Compare July 23, 2026 17:24

jr2bg added 2 commits July 23, 2026 17:41

Add primary owner to data types test

cdbe9fe

Merge remote-tracking branch 'origin/master' into feature/report-by-f…

97d0078

…uzzer-owner

jr2bg requested a review from vitaliset July 23, 2026 20:17

dylanjew approved these changes Jul 24, 2026

View reviewed changes

hunsche previously requested changes Jul 28, 2026

View reviewed changes

Merge branch 'master' into feature/report-by-fuzzer-owner

6b63182

dylanjew requested a review from hunsche July 29, 2026 15:39

dylanjew approved these changes Jul 29, 2026

View reviewed changes

Merge branch 'master' into feature/report-by-fuzzer-owner

bc9bec3

decoNR reviewed Aug 11, 2026

View reviewed changes

Comment thread src/appengine/handlers/fuzzers.py Outdated

jr2bg and others added 2 commits August 13, 2026 06:55

Merge branch 'master' into feature/report-by-fuzzer-owner

6901525

Removed duplicated cast for external_contribution

8d34bb4

jr2bg force-pushed the feature/report-by-fuzzer-owner branch from c011f99 to 8d34bb4 Compare August 13, 2026 20:21

Merge branch 'master' into feature/report-by-fuzzer-owner

b45a44b

Uh oh!

Conversation

jr2bg commented Jun 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Feature tests

Show “owner” textbox

Preconditions

Steps

Evidence

Show owner entry on Pantheon Audit Logs

Preconditions

Steps

Evidence

Uh oh!

dylanjew left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

dylanjew Jul 16, 2026

Choose a reason for hiding this comment

Uh oh!

dylanjew Jul 16, 2026

Choose a reason for hiding this comment

Uh oh!

decoNR Aug 11, 2026

Choose a reason for hiding this comment

Uh oh!

hunsche left a comment

Choose a reason for hiding this comment

Uh oh!

dylanjew commented Jul 28, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dylanjew left a comment

Choose a reason for hiding this comment

Uh oh!

decoNR left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

dylanjew commented Aug 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

jr2bg commented Jun 4, 2026 •

edited

Loading

dylanjew commented Jul 28, 2026 •

edited

Loading