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

On an unsaved file, Continue sends an empty query, resulting in bad completions #1293

Open
3 tasks done
coder543 opened this issue May 16, 2024 · 2 comments
Open
3 tasks done
Labels
bug Something isn't working

Comments

@coder543
Copy link

coder543 commented May 16, 2024

Before submitting your bug report

Relevant environment info

- OS: Linux
- Continue: latest published version
- IDE: VS Code

Description

I am editing a new, unsaved file. It has TypeScript code in it, and VS Code is in TypeScript mode. However, the completions are very bad and always the same. I checked the Continue "output" window, and I can see why.

It's not even trying to send content from the current file. As soon as I saved the file to disk, it seemed to start working normally.

I'm not sure if it is relevant, but I'm using VS Code over a "Remote - SSH" session.

To reproduce

No response

Log output

==========================================================================
==========================================================================
Settings:
contextLength: 4096
model: codegemma:7b-code-q8_0
maxTokens: 1024
stop: <|fim_prefix|>,<|fim_suffix|>,<|fim_middle|>,<|file_separator|>,<|fim_prefix|>,<|fim_suffix|>,<|fim_middle|>,<|file_separator|>,<end_of_turn>,<eos>,

,

,/src/,#- coding: utf-8,```,
function,
class,
module,
export,
import
temperature: 0.01
raw: true

############################################

<|fim_prefix|><|fim_suffix|><|fim_middle|>==========================================================================
==========================================================================
Settings:
contextLength: 4096
model: codegemma:7b-code-q8_0
maxTokens: 1024
stop: <|fim_prefix|>,<|fim_suffix|>,<|fim_middle|>,<|file_separator|>,<|fim_prefix|>,<|fim_suffix|>,<|fim_middle|>,<|file_separator|>,<end_of_turn>,<eos>,

,

,/src/,#- coding: utf-8,```,
function,
class,
module,
export,
import
temperature: 0.01
raw: true

############################################

<|fim_prefix|>
<|fim_suffix|>
<|fim_middle|>==========================================================================
==========================================================================
Completion:

import { Component, OnInit } from '@angular/core';
@coder543 coder543 added the bug Something isn't working label May 16, 2024
@sestinj
Copy link
Contributor

sestinj commented May 20, 2024

Ah yes the remote part seems like the important one, thanks for mentioning that detail. I know i'd fixed a similar bug recently for non-remote, but I'll take a second look at this. Were you on the latest pre-release version of the extension?

@coder543
Copy link
Author

I was just using whatever is in the VS Code extension store. I don't think it was a pre-release version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants