kirtivr

4 ms·

1.
by kirtivr 2mo ago
Congratulations on the launch. I love the idea and the execution. When I looked into this a while back I explored using ptrace() to add breakpoints and even add functions at specific line numbers. But ptrace is so slow, and it doesn't
2.
by kirtivr 3mo ago
Deepseek has always been better than people gave it credit for. You have to be careful with the inference provider though, Chinese providers are subject to laws that mandate data sharing with their government.
3.
by kirtivr 3mo ago
One big reason I can think of is to avoid vendor lock-in. This is why most enterprises use a multi-cloud setup, despite the increased complexity.
4.
by kirtivr 3mo ago
Here is a counterexample to whatever counterexample you have in mind - Most popular models on OpenRouter right now: https://openrouter.ai/models?categories=programming&order=mo... Top 7 are all open models.
5.
by kirtivr 3mo ago
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:
6.
by kirtivr 3mo ago
to be fair, coding agent harnesses have been becoming more and more complex. it's not an llm in a loop with tools anymore (as claude code was rumoured to be on HN).
7.
by kirtivr 3mo ago
A few different ways: - Copilot may be better at implementing features. We're better at investigating bugs and fixing them. - We handle huge context very easily. We specialize towards investigating large amounts of logs/metrics an
8.
by kirtivr 3mo ago
This is on our roadmap! At this time we are focussing on evaluation benchmarks like SWE-bench (verified). This is a simpler benchmark and does not really map well to investigating alerts that have a huge amount of context. But its a start.
9.
by kirtivr 3mo ago
Thank you! are you using any AI tools to debug productions issues at this time? Would love to have you join our Discord- https://discord.gg/XNXVD34P8
10.
by kirtivr 3mo ago
Hey satyamtiwary thanks so much for trying the product! We'd love to have you join our Discord: https://discord.gg/XNXVD34P8
11.
by kirtivr 3mo ago
Thanks. As teams move faster with AI generated code, the focus on quality and reliability will have to increase as well. And we will have to build better tools if we want to accelerate shipping velocity.
12.
by kirtivr 3mo ago
Thank you! are you using any AI tools to debug productions bugs at this time?
13.
by kirtivr 3mo ago
Nginx, Caddy, Flink and Firefox are some applications where we we've managed to consistently fix and reproduce reported bugs. Of course, we did not send the PRs to the repos seeing how they're already overloaded with them. Nginx f
14.
by kirtivr 3mo ago
We either mock or fake out the interfaces. I much prefer faking to mocking, because that still preserves a lot of the real-world behavior relevant to prod bugs. A full prod reproduction would be a holy grail, but probably only attainable fo
15.
by kirtivr 3mo ago
War story time? xD
16.
by kirtivr 3mo ago
On how does the mocking work, that's a really interesting question. We do a lot of AST parsing - for both code and build configuration languages. Even then, we still have to rely on the LLM to figure out a lot of the details. Making th
17.
by kirtivr 3mo ago
It's really nice to hear that. FixBugs was built because while investigating prod incidents, I had an epiphany. SWEs build tools to solve all types of problems, but we ourselves use the flakiest tools. While working at Google for examp
18.
by kirtivr 3mo ago
On Linux, we rely on a chroot-ed workspace at this time - although we are working on a prototype using the new landlock kernel interface ( https://github.com/Zouuup/landrun ). OSX is the best, we use the in-built (seatbe
19.
by kirtivr 3mo ago
Thank you so much. are you using any AI tools to debug productions issues at this time?
20.
by kirtivr 3mo ago
Thank you so much. are you using any AI tools to debug productions issues at this time?
21.
by kirtivr 3mo ago
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
22.
by kirtivr 3mo ago
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.
23.
by kirtivr 3mo ago
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 r
24.
Show HN: FixBugs – Reproduce production bugs and verify fixes(fixbugs.ai)
43 points by kirtivr 3mo ago|39 comments
25.
by kirtivr 4mo ago
Yeah, the problem reduces to trying to restrict a motivated model which is trying to exfiltrate data. That's a problem we are just now wrapping our minds around. It's not as simple as prompt sanitization. The model is the interpre
26.
by kirtivr 4mo ago
TIL. Thanks for that!
27.
by kirtivr 4mo ago
Is this an admission that prompt injection attacks can indeed not be blocked by an analysis based technique? If so many tools are straight up blocked, I would be very sceptical of the quality of the results.
28.
LLM agent performance is a distributed systems problem(fixbugs.ai)
2 points by kirtivr 4mo ago|0 comments
29.
by kirtivr 4mo ago
C++ is one of the languages less suited to the strengths of coding agents. The language which still supports C-style pointers, arbitrary datatype conversions, and inherits architecture-specific undefined behavior gives you too many ways to
30.
by kirtivr 4mo ago
Yeah, when you had multiple agents working on the same machine, branch isolation was no longer sufficient. A repository folder can only be on one branch at a time. A worktree is basically equivalent to a cp -R + git branch, which allows thi

More ›