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.
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.
Great tool to triage the reported issues in bugs and fix them swiftly. This will definitely improves your productivity.
Thank you so much.
are you using any AI tools to debug productions issues at this time?
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.
Great tool to triage and fix the issues in bug. Improves your productivity massively.
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.
very nice tool! helpful and I love it
Thank you so much.
are you using any AI tools to debug productions issues at this time?
It seems like a cool idea.
Thanks a lot!
I think FixBugs is most useful during high volume bug triage. This is where having a low false-positive async debugging agent is most helpful.