-
Notifications
You must be signed in to change notification settings - Fork 297
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
bug: Embedding will not update since 7 days #3636
Comments
The only workaround which helped was to delete the embedding file. Then it starts indexing new. |
Where do I find this file? I'm having the same issue. |
I want to bump up this issue. Embeddings blended with keywords are a more reliable context fetch mechanism than keyword alone. The cody-engine does not check the current commit hash with the one used during embedding correctly, If you need support fixing the cody-engine (I guess it is written in Go) then we can talk. |
This issue is marked as stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed automatically in 5 days. |
bump |
what's the point of embedding even a few days from now... |
For the context fetching in Cody exists two mechanism. one is the keyword search based on the prompt input and the other are with embeddings. 1 The keyword search is practical if you know the terms of the codebase. If code is changing, for example data structure, refactoring of functions etc, and the embeddings are outdated, then Cody will provide out-dated code. I made experiments with keyword search only and blended (keyword + embeddings) and the latter brings much more reliable context to the point. |
Closed because of changing embedding strategy |
Can I read somewhere what was changed? For now, in my project, it's all the same... |
Hello @kurutah |
Version
1.10.1 & latest pre-release
Describe the bug
When entering chat mode with the 'enhanced context' feature enabled, the embeddings failed to update after 24 hours, despite the code being current with the upstream repository on the 'main' branch.
Expected behavior
I anticipate receiving an update at least every 24 hours.
Additional context
The screenshot provided includes the commit history on the right side, the log of the 'Cody' output, and hints related to the commit hash.
The text was updated successfully, but these errors were encountered: