Closed erictraut closed 2 months ago
This will be fixed in the next release.
This turns out to be a long-standing bug that was exposed by a recent change. It was very subtle and occurred under very specific conditions, some of them relating to the specific order of evaluation which can easily change (e.g. based on whether you're hovering your mouse over a particular identifier immediately after editing a file). Interestingly, these conditions don't appear to occur anywhere in the large corpus of public code bases that we use for smoke testing pyright, which explains why the problem wasn't detected previously.
Thanks for providing the repro steps that allowed me to find and fix the issue.
This is addressed in pyright 1.1.377.
Discussed in https://github.com/microsoft/pyright/discussions/8778