-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Large Git repos aren't able to be indexed #3715
Comments
I'm using this to run: |
We have set a timeout for each embedding model request to keep the indexing time manageable. As a result, some requests may fail and trigger warnings. Please note that these warnings can be safely ignored. Tabby's background indexing job will incrementally re-index any failed chunks |
|
if you have a really large repo, that's somewhat expected. The only way to speed it up is to use more powerful model serving backend (and more powerful hardware ) to reduce the time of a cold start. Good thing is, once finished for the first run, the future incremental indexing shall be much faster. |
Thanks for offer the help to debug! I conducted a quick test by indexing 'bery' in Tabby's demo instance, and it functioned as anticipated; therefore, I was unable to replicate the issue. Here is the job log for reference: https://demo.tabbyml.com/jobs/detail?id=Gp3WX1 Could you try turn on debug log (e.g RUST_LOG=debug) to see if there's anything suspicious? |
The error can be safely disregarded if it occurs infrequently, especially when considered in the context of the total number of chunks processed. Can you share the command you used to start tabby? |
I'm using
I'm not sure if it occurs frequently or not, but there are 42 warnings like that for a repo of ~500 lines. |
I did the same with bevy, and up until the point of failure, there are 255 |
Describe the bug
I'm not sure if this is an issue about my device, because it isn't very powerful.
When using tabby to index repos, it always shows some amount of logs like these:
This is especially apparent on
https://github.com/bevyengine/bevy
, since I left it overnight and it still didn't finish indexing. As stated, I'm not sure if it's just my computer not being able to index very fast, but it even overnight it didn't finish.Information about your version
tabby 0.22.0
Information about your GPU
Apple M2 (4+4) @ 3.50 GHz
Additional context
Any repo will output those warning logs, but they still finish. For the bevy repo, it gets stuck on the example showcase main file
The text was updated successfully, but these errors were encountered: