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

Internal error while type checking #1219

Closed
goruck opened this issue May 2, 2021 · 2 comments
Closed

Internal error while type checking #1219

goruck opened this issue May 2, 2021 · 2 comments
Labels
bug Something isn't working fixed in next version (main) A fix has been implemented and will appear in an upcoming version

Comments

@goruck
Copy link

goruck commented May 2, 2021

Environment data

  • Language Server version: v2021.4.3
  • OS and version: Ubuntu 20.04.2 LTS
  • Python version (& distribution if applicable, e.g. Anaconda): 3.8.5

Expected behaviour

No internal error while type checking.

Actual behaviour

An internal error occurred while type checking file "/home/lindo/Develop/radar-ml/sgan.py": Error: Debug Failure. False expression.
at a.lock (/home/lindo/.vscode-server/extensions/ms-python.vscode-pylance-2021.4.3/dist/pyright-internal/src/analyzer/typeVarMap.ts:238:9)
at validateFunctionArgumentTypes (/home/lindo/.vscode-server/extensions/ms-python.vscode-pylance-2021.4.3/dist/pyright-internal/src/analyzer/typeEvaluator.ts:8080:24)
at callback (/home/lindo/.vscode-server/extensions/ms-python.vscode-pylance-2021.4.3/dist/pyright-internal/src/analyzer/typeEvaluator.ts:6349:28)
at useSpeculativeMode (/home/lindo/.vscode-server/extensions/ms-python.vscode-pylance-2021.4.3/dist/pyright-internal/src/analyzer/typeEvaluator.ts:17893:20)
at validateOverloadsWithExpandedTypes (/home/lindo/.vscode-server/extensions/ms-python.vscode-pylance-2021.4.3/dist/pyright-internal/src/analyzer/typeEvaluator.ts:6347:17)
at validateOverloadedFunctionArguments (/home/lindo/.vscode-server/extensions/ms-python.vscode-pylance-2021.4.3/dist/pyright-internal/src/analyzer/typeEvaluator.ts:6421:32)
at callback (/home/lindo/.vscode-server/extensions/ms-python.vscode-pylance-2021.4.3/dist/pyright-internal/src/analyzer/typeEvaluator.ts:7042:48)
at expandSubtype (/home/lindo/.vscode-server/extensions/ms-python.vscode-pylance-2021.4.3/dist/pyright-internal/src/analyzer/typeEvaluator.ts:3310:41)
at mapSubtypesExpandTypeVars (/home/lindo/.vscode-server/extensions/ms-python.vscode-pylance-2021.4.3/dist/pyright-internal/src/analyzer/typeEvaluator.ts:3326:13)
at ft (/home/lindo/.vscode-server/extensions/ms-python.vscode-pylance-2021.4.3/dist/pyright-internal/src/analyzer/typeEvaluator.ts:6960:28)

Logs

See problem message above from Visual Studio Code. 

Code Snippet / Additional information

XXX
@github-actions github-actions bot added the triage label May 2, 2021
@erictraut
Copy link
Contributor

Thanks for the bug report. This appears to be a duplicate of #1218, which I've already fixed.

@erictraut erictraut added bug Something isn't working fixed in next version (main) A fix has been implemented and will appear in an upcoming version and removed triage labels May 2, 2021
@jakebailey
Copy link
Member

This issue has been fixed in version 2021.5.0, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202150-5-may-2021

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working 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

3 participants