Skip to content

Conversation

@AashutoshMurthy
Copy link
Contributor

Some issues are not getting filed into the desired component of their code owners. This component is provided as a metadata.

The current change aims at emphasising this metadata component by removing the automatic component.

Please refer to b/438511288 for additional details.

@svasudevprasad
Copy link
Collaborator

/gcbrun


recovered_exception = None
try:
if issue_tracker.project == "google-buganizer":
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jonathanmetzman Do you see any issues with adding logs with this kind of data?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the TL;DR here is some of our fuzzers are finding bugs and trying to assign them to buganizer components where ClusterFuzz does not have access. So, it silently fails to create bugs in the component's where developers are expecting them.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@javanlacerda Please take a look when you have a moment

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you think the logging issue would be?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jonathanmetzman I think when I commented on this initially, I was concerned that ClusterFuzz instances will be logging potentially sensitive data in the form of buganizer components.

Upon further thought, only the owners of the instance will have access to these logs. So no, I don't think there is any issue with this, and it will help us to better assign issues to owners in our instance.

@AashutoshMurthy AashutoshMurthy force-pushed the update_component_id_logic branch from 479ef6c to 5b68ab1 Compare December 16, 2025 05:57
@svasudevprasad
Copy link
Collaborator

/gcbrun

@AashutoshMurthy AashutoshMurthy force-pushed the update_component_id_logic branch from 5b68ab1 to 1253c06 Compare December 18, 2025 06:20
@svasudevprasad
Copy link
Collaborator

/gcbrun

@AashutoshMurthy AashutoshMurthy force-pushed the update_component_id_logic branch 2 times, most recently from 4f13515 to e75acf8 Compare December 23, 2025 14:26
@AashutoshMurthy AashutoshMurthy force-pushed the update_component_id_logic branch from e75acf8 to 619b4b0 Compare January 7, 2026 05:30
@svasudevprasad
Copy link
Collaborator

/gcbrun

@AashutoshMurthy AashutoshMurthy force-pushed the update_component_id_logic branch from 619b4b0 to f3d1814 Compare January 7, 2026 18:39
Some issues are not getting filed into the desired component of their code owners. This component is provided as a metadata.

The current change aims at emphasising this metadata component by removing the automatic component.

Please refer to b/438511288 for additional details.
@AashutoshMurthy AashutoshMurthy force-pushed the update_component_id_logic branch from f3d1814 to 2be632c Compare January 9, 2026 04:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants