continuedev / continue

⏩ Continue is the leading open-source AI code assistant. You can connect any models and any context to build custom autocomplete and chat experiences inside VS Code and JetBrains
https://docs.continue.dev/
Apache License 2.0
19.43k stars 1.69k forks source link

Failed to load message bundle for a file when run launch extension and can't load extension gui page #3005

Open AfterStories opened 2 days ago

AfterStories commented 2 days ago

Before submitting your bug report

Relevant environment info

- OS:WINDOWS X64
- Continue version:The latest main branch code
- IDE version:The latest vscode and the latest ideaIC 2024

Description

When I use the command to install the dependencies .\scripts\install-dependencies.ps1 and then run Launch extension in vscode to debug the vscode plugin, I can see the plugin in the new vscode window that pops up, but it is very likely to be blank, without any gui content, and an error message will be seen in the DEBUG CONSOLE column in the main window: image

Failed to load message bundle for file c:\Users\hzheng057.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.6\out\extension

this error message come from file: C:\Users\hzheng057\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js

Why do I say that there is a high probability that it will always be blank? Because when I try to re-run the .\scripts\install-dependencies.ps1 command to install dependencies many times, one time I may succeed in seeing the gui correctly displayed in the extension window in the new pop-up window of vscode after startup.

In other words, I think that in the process of executing the .\scripts\install-dependencies.ps1 command or executing the Run Task->install al dependis task in vscode, there may be a step failure, but there is no obvious error log or warning, resulting in the failure of enabling the extension in the new window.

In addition, I can now see the extension page correctly in the new vscode window that pops up, but I still see an error message in the DEBUG CONSOLE column of the main vscode:

Failed to load message bundle for file c:\Users\hzheng057.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.6\out\extension

This error message is like a devil's curse. Every time I see it, it is very likely that the extension page in my new vscode window is blank and cannot be loaded correctly.

I hope you can quickly check the possible reasons for this issue

To reproduce

  1. .\scripts\install-dependencies.ps1
  2. Launch extension
  3. Error message show in DEBUG CONSOLE tab: Failed to load message bundle for file c:\Users\hzheng057\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.6\out\extension
  4. In the new vscode window that pops up, the extended window is blank and the gui page cannot be loaded

Log output

3. Error message show in DEBUG CONSOLE tab:
`Failed to load message bundle for file c:\Users\hzheng057\.vscode\extensions\ms-edgedevtools.vscode-edge-devtools-2.1.6\out\extension`
AfterStories commented 22 hours ago

Now, according to my experience, when this happens, I need to use Ctrl+Shift+P in the newly popped-up vscode window, and then execute Developer:Reload Window to reload the window, so that the blank extension interface can re-display the UI.

Or, when I kill all processes with vscode in the system process manager, reopen vscode and start the extension, this problem will be solved.

So I guess that the file reported in the error is in a state of being occupied by a process, which causes me to be unable to load this file when I restart the extension multiple times. This is just my guess. So if you have any ideas about this problem, you can consider adding a step to kill the related processes that already existed last time in the script that starts the extension.