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

Log messages not written to output panel - filesystem errors #3785

Open
3 tasks done
ingo-eichhorst-ionos opened this issue Jan 20, 2025 · 1 comment
Open
3 tasks done
Assignees
Labels
ide:vscode Relates specifically to VS Code extension kind:bug Indicates an unexpected problem or unintended behavior "needs-triage"

Comments

@ingo-eichhorst-ionos
Copy link

Before submitting your bug report

Relevant environment info

- OS: MacOS 15.2 (24C101) - M1 (ARM)
- Continue version: 0.9.251
- IDE version: VS Code - Version: 1.96.2 (Universal)
- Model: GPT-4o

- config.json:
  
  "models": [
    {
      "title": "codestral",
      "model": "codestral-latest",
      "provider": "mistral",
      "apiKey": "random_string"
     }  ...
  ]

Description

"Continue - LLM Prompt/Completion" Log messages are not written to the output. (That makes debugging extremely chellanging) Instead there are warnings and error message in the console.

console.ts:137 [Extension Host] rejected promise not handled within 1 second: Error (FileSystemError): Unable to resolve filesystem provider with relative file path 'output:extension-output-Continue.continue-%231-Continue - LLM Prompt/Completion'
console.ts:137 [Extension Host] stack trace: Error (FileSystemError): Unable to resolve filesystem provider with relative file path 'output:extension-output-Continue.continue-%231-Continue - LLM Prompt/Completion'
	at Qi.e (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:115:9853)
	at Object.readFile (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:115:7581)
	at async _RecentlyEditedTracker.insertRange (/Users/ieichhorst/.vscode/extensions/continue.continue-0.9.251-darwin-arm64/out/extension.js:605296:27)
mainThreadExtensionService.ts:78 [Continue.continue]Unable to resolve filesystem provider with relative file path 'output:extension-output-Continue.continue-%231-Continue - LLM Prompt/Completion'
mainThreadExtensionService.ts:79 Error (FileSystemError): Unable to resolve filesystem provider with relative file path 'output:extension-output-Continue.continue-%231-Continue - LLM Prompt/Completion'
	at Qi.e (/Applications/Visual…Process.js:115:9853)
	at Object.readFile (/Applications/Visual…Process.js:115:7581)
	at async _RecentlyEditedTracker.insertRange (vscode-file://vscode…ension.js:605296:27)

Image

To reproduce

  1. Happens with every chat message i sent
  2. See the empty logs below

Log output

##### Completion options #####
{
  "contextLength": 32768,
  "model": "codestral-latest",
  "maxTokens": 4096
}

##### Request options #####
{}

##### Prompt #####
<system>


<user>
@dosubot dosubot bot added ide:vscode Relates specifically to VS Code extension kind:bug Indicates an unexpected problem or unintended behavior labels Jan 20, 2025
@Patrick-Erichsen
Copy link
Collaborator

Thanks for the heads up here @ingo-eichhorst-ionos !

Some recent changes we made to our URI schemes appears to be the culprit:

mainThreadExtensionService.ts:78 [Continue.continue]Unable to resolve filesystem provider with relative file path 'output:extension-output-Continue.continue-%231-Continue - LLM Prompt/Completion'

cc'ing @RomneyDa here who has more context on the URI updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ide:vscode Relates specifically to VS Code extension kind:bug Indicates an unexpected problem or unintended behavior "needs-triage"
Projects
None yet
Development

No branches or pull requests

3 participants