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

Jupyter Notebook syntax highlighting breaks for multiroot workspace when root is added #6755

Open
Real-Gecko opened this issue Dec 9, 2024 · 4 comments
Assignees
Labels
needs repro Issue has not been reproduced yet

Comments

@Real-Gecko
Copy link

Does this issue occur when all extensions are disabled?: Yes, except Python and 'Jupyter'
Image

  • VS Code Version: 1.95.3
  • OS Version: Arch Linux

Steps to Reproduce:

  1. Clone following repo https://github.com/Real-Gecko/vscode-jupyter-bug
  2. Open testing.code-workspace in VSCode
  3. With Explorer open dir1/.jupyter/testing.ipynb
  4. Note that syntax highlighting and code analysis is completely broken, despite cell execution is successful
    Image
  5. Open testing.code-workspace in editor and comment out this section
        {
            "path": ".",
            "name": "root"
        }
  1. Restart VSCode and reopen notebook, now syntax highlighting works.
  2. So, it only happens when workspace root folder(one with .code-workpsace file) exist in list of folders
@rebornix rebornix transferred this issue from microsoft/vscode Dec 9, 2024
@rebornix rebornix removed their assignment Dec 9, 2024
@karthiknadig karthiknadig transferred this issue from microsoft/vscode-python Dec 10, 2024
@github-actions github-actions bot added the needs repro Issue has not been reproduced yet label Dec 10, 2024
@rchiodo
Copy link
Contributor

rchiodo commented Dec 10, 2024

Thanks for logging an issue. It looks like pylance is crashing or is not being started for some reason.

Can you include the output as described here?
https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue

@Real-Gecko
Copy link
Author

Added

    "settings": {
        "python.analysis.logLevel": "Trace"
    }

to .code-workspace, here's the result
pylance.trace.log

@rchiodo
Copy link
Contributor

rchiodo commented Dec 10, 2024

Thanks, I can reproduce the problem. The workspace folders being inside one another is messing up the import paths for some reason.

@Real-Gecko
Copy link
Author

By the way, if I just open folder(root one) everything works as expected, only if I open .code-workspace syntax highlighting breaks, might be important detail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs repro Issue has not been reproduced yet
Projects
None yet
Development

No branches or pull requests

4 participants