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

Pylance is not working on vscode.dev/github.dev #2235

Closed
luabud opened this issue Jan 10, 2022 · 3 comments
Closed

Pylance is not working on vscode.dev/github.dev #2235

luabud opened this issue Jan 10, 2022 · 3 comments
Assignees
Labels
fixed in next version (main) A fix has been implemented and will appear in an upcoming version

Comments

@luabud
Copy link
Member

luabud commented Jan 10, 2022

Environment data

  • Language Server version: v2022.1.0
  • OS and version: Windows 10
  • Python version (& distribution if applicable, e.g. Anaconda): N/A

Expected behaviour

When I open a Python file on the browser, I get semantic highlight and simply auto completions for Python files

Actual behaviour

Pylance seems to not be working at all when in vscode.dev/github.dev

Logs

[Info  - 9:25:59 AM] Pylance language server 2022.1.0 (pyright 5829dcbb) starting
[Info  - 9:25:59 AM] Server root directory: /
[Info  - 9:25:59 AM] No configuration file found.
[Info  - 9:25:59 AM] No pyproject.toml file found.
[Warn  - 9:25:59 AM] stubPath /pvscc-logo/typings is not a valid directory.
Search paths for /pvscc-logo
  /typeshed-fallback/stdlib
  /pvscc-logo
  /pvscc-logo/typings
  /typeshed-fallback/stubs/...
  /bundled/stubs
[Info  - 9:25:59 AM] Searching for source files
[Error - 9:25:59 AM] File or directory "/pvscc-logo" does not exist.
[Info  - 9:25:59 AM] No source files found.

Code Snippet / Additional information

XXX
@heejaechang
Copy link
Contributor

Thank you for the report.

it looks like it got broke.

image

taking a look.

@heejaechang heejaechang self-assigned this Jan 10, 2022
@heejaechang heejaechang added the needs investigation Could be an issue - needs investigation label Jan 10, 2022
@github-actions github-actions bot removed the triage label Jan 10, 2022
@github-actions github-actions bot removed the triage label Jan 10, 2022
@heejaechang heejaechang added triage and removed needs investigation Could be an issue - needs investigation labels Jan 10, 2022
@luabud
Copy link
Member Author

luabud commented Jan 10, 2022

thanks for looking into it!

@judej judej added the needs investigation Could be an issue - needs investigation label Jan 10, 2022
@github-actions github-actions bot removed the triage label Jan 10, 2022
@heejaechang heejaechang added fixed in next version (main) A fix has been implemented and will appear in an upcoming version and removed needs investigation Could be an issue - needs investigation labels Jan 10, 2022
@bschnurr
Copy link
Member

This issue has been fixed in version 2022.1.1, which we've just released. You can find the changelog here: CHANGELOG.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed in next version (main) A fix has been implemented and will appear in an upcoming version
Projects
None yet
Development

No branches or pull requests

4 participants