-
Notifications
You must be signed in to change notification settings - Fork 2.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
autocomplete not work #3573
Comments
This issue may have been fixed in #3536, if just completion at the end of file content is not working. |
@lkk214 autocompletion works when the cursor is not at the end of file content |
@ysrotciv are you able to try 0.0.84? You'll need to install from EAP. There were some other folks having issues with autocomplete in Pycharm on 0.0.83 (e.g. #3577), but it appears to be fixed in 0.0.84 |
After I upgrade continue to 0.0.84, there is still error in core.log and autocomplete works. |
@Patrick-Erichsen I have never encountered this error log. Maybe it is related to the sagemaker provider. I have not used it. |
I see the same issue with Bedrock. It sometimes works, but most of the time (even when not at end of file):
Continue 0.0.84, IJ 2024.1, Claude 3.5 Sonnet |
@bdavj I believe your specific issue is actually a different problem, see this thread: #3440 We also advise against using Sonnet for autocomplete as it isn't trained for FIM and has high latency - Codestral is a much better option. See here for more info: https://docs.continue.dev/customize/model-types/autocomplete |
Many thanks for the pointer. Are there any models within bedrock that are likely to work? (Adding another API/vendor isn't really an option unfortunately) |
@bdavj at the moment no, but Poolside and Mistral both have autocomplete models coming to Bedrock in the neat future. Just updated our docs to mention this: https://github.com/continuedev/continue/pull/3789/files#diff-8c78666b9f1b0d68e9c441d6fa93fa2476e4a6a08426f5b8f082e69830c09939R44 |
Before submitting your bug report
Relevant environment info
The text was updated successfully, but these errors were encountered: