[soohoonchoi]

Hey sorry to hear that, a couple of things:

- processing is usually stuck at 99% because when we order the components of the repository by file-directory dependency and ast dependency, there are a lot, LOT more leaves than the internal nodes + the root. Since we have to have the results of the dependency before we move on, moving up the dependency chain with llm calls take a while. This is even more pronounced when nearing the root for completion. We are working on optimizing this flow as it is very annoying for us as well.

- "Error: Internal error while locating sources": this is embarrassing but we did experience a database outage today (I wonder why) some repositories have a faulty status. It should be back up now and we are working to recover/reprocess the repos that have failed during the outage (including dvx/lofi)

- "Onboard" that was our previous name, this has slipped through the cracks, thanks for pointing it out!

We are trying to parse most of the popular open source repos (we have processed repos like python, vscode, etc). We are hoping to fully process the linux kernel soon as well (a personal benchmark of mine).

[pitaj]

Just wanted you to know that the formatting of your quotes is messed up. You probably need to add some more linebreaks.

[MikePlacid]

> processing is usually stuck at 99%

Why call it 99% then, call it 49%.

[dakshgupta]

Noted - I think Soohoon meant to use the word "often" and not usually. That said, you're right, counting completed nodes would be a more accurate way of measuring progress.