Live data from Hacker News

Show HN: FixBugs – Reproduce production bugs and verify fixes

fixbugs.ai

1–10 of 46 posts

Show HN: FixBugs – Reproduce production bugs and verify fixes

#1
I built FixBugs, an agent that ingests the rich context surrounding production bugs to reproduce them in a sandbox and generate verified fixes. It's available in the form of a self-hosted VSCode extension and as a Github app:

VSCode Extension: https://fixbugs.ai/go/vscode-extension

  - full code and data privacy.
  - zero data retention models opted out of training.
GitHub App: https://fixbugs.ai/go/github-app

  - we do access your code temporarily.
  - pick a repo to install FixBugs on.
What motivated me to build FixBugs were my years being on-call at Google and VMware. How many hours did I spend gathering logs, traces, reviewing metrics, and reading code only to find that,

* Some context was missing.

* The bug wasn't reproducible.

* The alert was caused by a transient infrastructure issue.

Too many. Inefficiency in investigating staging/production bugs has a real cost, and it's paid both by developers and customers.

Current capabilities:

  - Reproduce the bug.

  - Identify the root cause.

  - Generate a fix.

  - Verify the fix.

  - Review the generated code using multiple AI models to help catch potential regressions.
Do try it and let me know what you think!

I'd especially love feedback from engineers who work with distributed systems or handle high-volume production bug triage.

Show HN: FixBugs – Reproduce production bugs and verify fixes
fixbugs.ai

Re: Show HN: FixBugs – Reproduce production bugs and verify fixes

#3
A different approach that we took to root causing bugs that you may find interesting is that we first try to reproduce the bug before coming up with a fix for it.

This is essentially a (RCA Repro test case) loop until we're recreated the bug. If our attempts are not converging and we’re on the wrong track, we ask for human input.

Re: Show HN: FixBugs – Reproduce production bugs and verify fixes

#10
post #8

Also, How is the VSCode extension reproducing the bug on my machine? That sounds dangerous.

Oh the repro runs in an isolated sandbox, and all interactions outside the sandbox (with lets say other services or databases) are mocked. The repro harness doesn't have access outside of it.

This also allows us to inject various types of faults, which is helpful with debugging more complex systems.

Post reply on HN