Skip to content
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

Closed
PriNova opened this issue Mar 30, 2024 · 10 comments
Closed

bug: Embedding will not update since 7 days #3636

PriNova opened this issue Mar 30, 2024 · 10 comments
Labels
bug Something isn't working clients/vscode cody

Comments

@PriNova
Copy link
Collaborator

PriNova commented Mar 30, 2024

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.

Screenshot 2024-03-30 110826

@PriNova PriNova added bug Something isn't working clients/vscode labels Mar 30, 2024
@github-actions github-actions bot added the cody label Mar 30, 2024
@PriNova
Copy link
Collaborator Author

PriNova commented Mar 30, 2024

The only workaround which helped was to delete the embedding file. Then it starts indexing new.

@FelipeMorandini
Copy link

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.

@PriNova
Copy link
Collaborator Author

PriNova commented May 28, 2024

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.

Copy link

github-actions bot commented Aug 4, 2024

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.

@github-actions github-actions bot added the Stale label Aug 4, 2024
@PriNova
Copy link
Collaborator Author

PriNova commented Aug 4, 2024

bump

@kurutah
Copy link

kurutah commented Aug 7, 2024

what's the point of embedding even a few days from now...

@PriNova
Copy link
Collaborator Author

PriNova commented Aug 8, 2024

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.
The embeddings are more like a fuzzy search, but understands code structure, code semantics and so on.
Combined in Cody are a very high reliable fetching mechanism for context in my experience.

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.

@github-actions github-actions bot removed the Stale label Aug 11, 2024
@PriNova
Copy link
Collaborator Author

PriNova commented Aug 15, 2024

Closed because of changing embedding strategy

@PriNova PriNova closed this as completed Aug 15, 2024
@kurutah
Copy link

kurutah commented Aug 16, 2024

Closed because of changing embedding strategy

Can I read somewhere what was changed? For now, in my project, it's all the same...

@PriNova
Copy link
Collaborator Author

PriNova commented Aug 19, 2024

Can I read somewhere what was changed? For now, in my project, it's all the same...

Hello @kurutah
The changes are an iterative process and are not yet available as a stable version. As soon as the process is complete, this will certainly be announced in the blog at https://sourcegraph.com/blog

@sqs sqs closed this as not planned Won't fix, can't repro, duplicate, stale Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working clients/vscode cody
Projects
None yet
Development

No branches or pull requests

4 participants