Thanks, I grabbed both IDs. I’ll pass them to the BugBot team so they can check the logs for those exact runs and compare them to the bug detection stage where it gets stuck in other reports. Once we know the root cause, I’ll reply in the thread.
@rushil, if you catch a repro in the monorepo, drop the serverGenReqId_... here from bugbot run verbose=true. Then we can compare two different load profiles in the same ticket.
On Autofix, quick answer:
- Autofix doesn’t re-run on existing comments by itself. It triggers when BugBot posts a new comment, or when you manually trigger it.
- The split between enable on all comments vs on specific ones is about the trigger mode in the dashboard:
- Auto on all: every BugBot note immediately starts the Cloud Agent to try to fix it. Handy, but it burns Cloud Agent quota fast, especially on big PRs with lots of notes.
- Manual or specific ones: Autofix only runs when you decide to trigger it on a specific comment, like via a reply or a button. The idea is you often close half the notes yourself in a minute, and Autofix only makes sense for the ones that would take you 10 to 20 minutes to investigate and fix. This is about saving Cloud Agent credits, not about severity.
A severity filter as a separate setting is a feature request, separate thread: Enabling bugbot to autofix low-complexity bugs (!= low severity)