Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Infinite loading of FIM when in remote VSCode(SSH) having opened unsaved interactive Jupyter tab. #310

Open
AndrewRocky opened this issue Sep 11, 2024 · 2 comments

Comments

@AndrewRocky
Copy link
Contributor

Describe the bug
I'm using VSCode from a Windows machine connected to Linux via SSH.
When there is an unsaved Interactive Jupyter window in the tabs list - Twinny gets stuck on autocomplete (in ALL tabs).

To Reproduce

  1. When in SSH remote window (not sure if this is important)
  2. Open Interactive Jupyter window (extension: https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter) - Command Pallete -> Jupyter: Create Interactive Window
  3. Go to any other tab and start typing (to trigger FIM)
  4. FIM doesn't stop loading (gets an error in logs)

Expected behavior
FIM to work properly.
(Maybe it should ignore the file that triggers an error?)

Logging

  ERR cannot open vscode-remote://attached-container%2B7b22636f6e7461696e65724e616d65223a222f6a757079746572227d@ssh-remote%2Bc590/Interactive-1.interactive. Detail: Unable to read file 'vscode-remote://attached-container+7b22636f6e7461696e65724e616d65223a222f6a757079746572227d@ssh-remote+c590/Interactive-1.interactive' (Error: Unable to resolve nonexistent file 'vscode-remote://attached-container+7b22636f6e7461696e65724e616d65223a222f6a757079746572227d@ssh-remote+c590/Interactive-1.interactive'): CodeExpectedError: cannot open vscode-remote://attached-container%2B7b22636f6e7461696e65724e616d65223a222f6a757079746572227d@ssh-remote%2Bc590/Interactive-1.interactive. Detail: Unable to read file 'vscode-remote://attached-container+7b22636f6e7461696e65724e616d65223a222f6a757079746572227d@ssh-remote+c590/Interactive-1.interactive' (Error: Unable to resolve nonexistent file 'vscode-remote://attached-container+7b22636f6e7461696e65724e616d65223a222f6a757079746572227d@ssh-remote+c590/Interactive-1.interactive')
    at o.$tryOpenDocument (vscode-file://vscode-app/c:/Users/edited/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:2460:132808)

API Provider
oobabooga

Chat or Auto Complete?
FIM (auto complete)

Model Name
starcoder2-15b

Desktop (please complete the following information):

  • Windows 11 (VSCode client) -> SSH into Ubuntu 20.04 (VSCode server)
  • Extension version: v3.16.2
  • From VSCode -> About:
Version: 1.93.0 (user setup)
Commit: 4849ca9bdf9666755eb463db297b69e5385090e3
Date: 2024-09-04T13:02:38.431Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.22631

Additional context
Chat works normally though (without embeddings - their provider has always been broken for me)

@AndrewRocky AndrewRocky changed the title Infinite loading of FIM when in remote VSCode(SSH) having open unsaved interactive Jupyter tab. Infinite loading of FIM when in remote VSCode(SSH) having opened unsaved interactive Jupyter tab. Sep 11, 2024
@FanaticPythoner
Copy link

Same issue for me. Ollama.

@AndrewRocky
Copy link
Contributor Author

Additional very similar issue:
Same behavior when there is an unsaved .yaml from Kubernetes extension in tabs (extension ms-kubernetes-tools.vscode-kubernetes-tools).

How to reproduce

  1. With Twinny: File Context Enabled > True
  2. In Kubernetes extension open any object's YAML (using button 'Load' in context menu):
    {6747DC31-1230-4C34-A8AA-C39AF0C839CC}
  3. It will open tab like this:
    {38E59F7A-E7FF-4274-9DE7-2E0C2CB6B38A}
  4. Without saving that YAML go to another tab and start typing something - FIM loading won't stop.

Suggestion

Can we just ignore files that cannot be opened?

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants