-
Notifications
You must be signed in to change notification settings - Fork 767
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
An internal error occurred while type checking file: RangeError: Maximum call stack size exceeded #825
Comments
Thanks for reporting the bug. We've identified and fixed one potential cause for this. Please try the next release of Pylance (which should be published in the next couple of days) and let us know if you still see the problem. |
This issue has been fixed in version 2021.1.1, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202111-13-january-2021 |
I am now on I have since published the "offending" source code here. Open the file Stack trace for 3.8.6:
Stack trace for 3.9.1:
|
@harenbrs, thanks for the repro steps. I was able to find and fix the problem. You are using |
Excellent, many thanks for dealing with it so quickly. Also happy to be making history, of a kind 😉 |
This issue has been fixed in version 2021.1.2, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202112-20-january-2021 |
dont think its been resolved as im having that issue right now. |
The original bug was definitely fixed. If you're experiencing a similar symptom, please file a new bug. And if you can provide a minimal code snippet that exhibits the problem, that would be really helpful. |
Environment data
Expected behaviour
Type checking functions correctly
Actual behaviour
Type checking throws an error at the top of the file
Logs
Code Snippet / Additional information
Code is closed source at the moment, and I haven't been able to find a minimum-reproducible example.
The stack trace to my eyes looks different from the recently closed similar issues.
The text was updated successfully, but these errors were encountered: