kevinlu1248

9 ms·

61.
by kevinlu1248 3y ago
Thanks, and I'm glad to hear! I'm Will's co-founder btw. Just wondering, what's the PR about?
62.
by kevinlu1248 3y ago
Yup! We used to use https://synclinear.com/ but you can also use Zapier to automatically redirect Linear issues to GitHub. It's a nice experience since we also had a Discord to Linear hook.
63.
by kevinlu1248 3y ago
This is interesting, I'll take a look. My main concern with running this in production is that there is more text data in the world than code. Further, a pure tree-manipulation model has less explainabilities since you can always ask G
64.
by kevinlu1248 3y ago
For editing code there's a decent chance of syntax errors or undefined variables since it's only modifying a subset of the code.
65.
by kevinlu1248 3y ago
Ya I think forcing correct syntax at the generation level likely will not be extremely beneficial. At Sweep, we iterate the language models on linters and type-checkers using GitHub Actions and it yields better results.
66.
by kevinlu1248 3y ago
Thanks! The repo is just the backend that runs the GitHub webhooks. We used to have a "chat with your code" client but stopped supporting it. Now it's only the GitHub interface with creating tickets and comments.
67.
by kevinlu1248 3y ago
Yup it's based on the aider blogs. They're perfect for our use case and are very reliable compared to our old attempts.
68.
by kevinlu1248 3y ago
Feel free to use the algo! Happy to help and reach out if you need help with implementation!
69.
by kevinlu1248 3y ago
For others in this thread, this algo is now publicly accessible in LlamaIndex at https://github.com/jerryjliu/llama_index/blob/e567e6a20cf89b...
70.
by kevinlu1248 3y ago
Update: this algo is now publicly accessible in LlamaIndex at https://github.com/jerryjliu/llama_index/blob/e567e6a20cf89b...
71.
by kevinlu1248 3y ago
Here's some of the papers: https://arxiv.org/abs/1911.09983 and https://aclanthology.org/2021.findings-acl.384.pdf
72.
by kevinlu1248 3y ago
I feel the same, benchmarking in general is a pain but a good benchmark for us could go a long way.
73.
by kevinlu1248 3y ago
Like stochastically generate into an intermediate representation that can be procedurally compiled to code right?
74.
by kevinlu1248 3y ago
This is really interesting, will take a look. So is this basically English to code translation?
75.
by kevinlu1248 3y ago
Not a great answer but we are open-source so forking us is an option.
76.
by kevinlu1248 3y ago
From our experience, single or few line replacements generally fine, since many of the changes are many few-line changes in multiple spots accross multiple files. We also provide surrounding context for the search-and-replace pairs, which h
77.
by kevinlu1248 3y ago
Yup, saw a few papers about this over the past two years, using graph neural networks for code generation. There's also another thread below on this topic. Edit: Here's some of the papers: https://arxiv.org/abs&#x2
78.
by kevinlu1248 3y ago
Definitely. I prefer the sentence-transformers ones since they have been fine-tuned on codesearchnet. I'm also really excited about the latest gte models by Alibaba, their smallest model is the size of MiniLM L6 but beats MPNet.
79.
by kevinlu1248 3y ago
We have a similar method under the hood, except it's purely text-based search-and-replace. The model decides what to replace. It seems to be consistent and is easy to implement.
80.
by kevinlu1248 3y ago
Shot an email. Thanks!
81.
by kevinlu1248 3y ago
This is interesting, I'm wondering what you mean by AST substitution. Is this like an agent that traverses the tree and picks what to edit? Is this language model based? Also, thankfully we don't support too many uncommon language
82.
by kevinlu1248 3y ago
We used to use line numbers but it became problematic so we switched over to search-and-replace pairs, which works significantly better. The only potential problems are with setting up a fuzzy search system since sometimes the search doesn&
83.
by kevinlu1248 3y ago
Which app? We did notice a few visual errors a while back.
84.
by kevinlu1248 3y ago
That would be awesome. Let me know when it's out and I'd love to try it out.
85.
by kevinlu1248 3y ago
I'm glad to hear! Let me know if you need more questions or are interested in implementing this chunking algo.
86.
by kevinlu1248 3y ago
Hey thanks for showing this dashboard. There's some crazy analytics in here, the tool looks awesome!
87.
by kevinlu1248 3y ago
We got rid of it. Our new edit framework works around search-and-replace pairs with an example at https://github.com/sweepai/sweep/blob/d37dda3a626f09dea3b322...
88.
by kevinlu1248 3y ago
From my experience, GPT-4 never makes syntax errors directly but when making edits to existing code it's harder to prevent these syntax errors from appearing. We used to add a second pass to check for these syntax errors. It also frequ
89.
by kevinlu1248 3y ago
This is interesting. I'm taking a read on this.
90.
by kevinlu1248 3y ago
That's interesting, I've seen a few papers about this. I'm personally curious about editing syntax trees using language models, since it would prevent syntax errors altogether.

More ›