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

Failed to load message bundle in debug function #19929

Closed
slion-L opened this issue Oct 2, 2022 · 1 comment
Closed

Failed to load message bundle in debug function #19929

slion-L opened this issue Oct 2, 2022 · 1 comment
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug

Comments

@slion-L
Copy link

slion-L commented Oct 2, 2022

Behaviour

Expected vs. Actual

i use the source code to generate the vsix file.
open a python file and first time click "Run and Debug"
the quick pick window should shows "Select a debug configuration" "Debug Configuration" "Python File" and so on.
but every item shows "Failed to load message bundle. See console for details"
if i press "F5", everything is ok.

Steps to reproduce:

  1. git clone https://github.com/microsoft/vscode-python
  2. cd vscode-python
  3. npm ci
  4. pip install black
  5. npx gulp installPythonLibs
  6. npm run package
  7. install the vsix
  8. open a python file
  9. click "Run and Debug"
  10. the quick pick window shows many "Failed to load message bundle. See console for details"

Diagnostic data

  • Python version (& distribution if applicable, e.g. Anaconda): 3.9.12
  • Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Conda
  • Value of the python.languageServer setting: Default
Output for Python in the Output panel (ViewOutput, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings


languageServer: "Jedi"

linting
• enabled: false
• flake8Args: "<placeholder>"
• flake8Enabled: true

sortImports
• args: "<placeholder>"

formatting
• provider: "black"

@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Oct 2, 2022
@karthiknadig karthiknadig added bug Issue identified by VS Code Team member as probable bug area-debugging labels Oct 3, 2022
@paulacamargo25 paulacamargo25 removed the triage-needed Needs assignment to the proper sub-team label Oct 24, 2022
@paulacamargo25 paulacamargo25 removed their assignment Oct 24, 2022
@paulacamargo25 paulacamargo25 added needs PR Ready to be worked on debt Covers everything internal: CI, testing, refactoring of the codebase, etc. labels Oct 24, 2022
@karthiknadig karthiknadig removed the debt Covers everything internal: CI, testing, refactoring of the codebase, etc. label Nov 3, 2022
@paulacamargo25
Copy link

Im closing this issue, because with the new localization API this error no longer exists.

@paulacamargo25 paulacamargo25 removed the needs PR Ready to be worked on label Jun 2, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jul 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging bug Issue identified by VS Code Team member as probable bug
Projects
None yet
Development

No branches or pull requests

3 participants