-
Notifications
You must be signed in to change notification settings - Fork 27
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
Copy does not create a new chunk #19
Comments
The chunk is added in the extra context and is visible if you get it with Ctrl+Shift+, . However, seems that there is a problem with the request. I will research it. |
I've noticed that sometimes llama.cpp server enters a specific state and become unresponsive (not yet sure when and how). While in this state the log is: There are other cases when the chunk is not added and there is no request - if it is too small or if it is identical with an existing chunk, but most probably this is not the reason for this bug. |
@igardev This is normal behavior when there are more than one VS Code instances running at the same time. Each one would have a different context accumulated in it's ring buffer and when you switch between them, the |
@ggerganov Yes, I have two running instances of VS Code. We could add a remark about that in the ReadMe.md file. |
When a block is copied with Ctrl+C or Cmd+C, the copied text should be added as a chunk in the extra context. Currently, this does not seem to happen. To reproduce, I copy a chunk of text and way to see a request to the server, but there is no such request.
Version: 0.0.6
The text was updated successfully, but these errors were encountered: