Continue fails autocomplete on remote files

[pmatos]

Before submitting your bug report

• [X] I believe this is a bug. I'll try to join the Continue Discord for questions
• [X] I'm not able to find an open issue that reports the same bug
• [X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: Linux
- Continue: 0.8.15
- IDE: VSCode 1.87.2

There's an Uncaught error in Runtime Status:
`Cannot read properties of undefined (reading 'repository')`

Description

When working on a remote project, opened through remote-ssh, I am getting when trying to autocomplete:

Unable to read file '/home/pmatos/dev/Foo/Stack.cpp' (Error: Unable to resolve nonexistent file '/home/pmatos/dev/Foo/Stack.cpp')

My file does not indeed exist locally, which is where I assume Continue is looking for it but only remotely.

To reproduce

1. Setup autocomplete with continue.
2. Open remote project
3. Start typing
4. autocomplete fails.

Log output

No response

[sestinj]

@pmatos Is this still happening on the latest version of Continue (0.8.23) and pre-release? (0.9.x)

[benrosenblum]

@sestinj This problem also happens to me while working with vscode running on windows with a repo inside WSL. I still get the tab autocompletions, but I get the popup with the non-existent file error intermittently. My completions are also always single-line despite setting multiline to "always" in the config, maybe this has something to do with that. I'm using ollama for tab completions and embeddings, and openai for interactive use.

[benrosenblum]

@pmatos In case you're still having this issue, I'll add here what I mentioned on #1099 that fixed this issue for me among others while using WSL. Since WSL is remote vscode, this solution might solve your problem as well. No credit to me, it came from the Discord.

    "remote.extensionKind": {
        "continue.continue": [
            "workspace"
        ]
    }

[pmatos]

@pmatos In case you're still having this issue, I'll add here what I mentioned on #1099 that fixed this issue for me among others while using WSL. Since WSL is remote vscode, this solution might solve your problem as well. No credit to me, it came from the Discord.

    "remote.extensionKind": {
        "continue.continue": [
            "workspace"
        ]
    }

Thanks - is this for vscode settings?

[pmatos]

@pmatos In case you're still having this issue, I'll add here what I mentioned on #1099 that fixed this issue for me among others while using WSL. Since WSL is remote vscode, this solution might solve your problem as well. No credit to me, it came from the Discord.

    "remote.extensionKind": {
        "continue.continue": [
            "workspace"
        ]
    }

Thanks - is this for vscode settings?

Confirmed - it is. :)

[pmatos]

@pmatos In case you're still having this issue, I'll add here what I mentioned on #1099 that fixed this issue for me among others while using WSL. Since WSL is remote vscode, this solution might solve your problem as well. No credit to me, it came from the Discord.

    "remote.extensionKind": {
        "continue.continue": [
            "workspace"
        ]
    }

Thanks - is this for vscode settings?

Confirmed - it is. :)

But it's still not working. Are there any debugging logs for these issues in Continue that I can look at?

[nejch]

Just chiming in to add one of my colleagues had this issue (Windows host to Linux remote), after switching to the latest prerelease and configurig https://github.com/continuedev/continue/issues/1107#issuecomment-2058037393, this solved the issue for him.