Closed ottumm closed 1 year ago
Thanks for reporting this. Are you able to narrow down the problem to a particular piece of code? Is the code base publicly accessible?
The codebase isn't public, but I'll see if I can narrow it down to a minimal reproducible case.
Thanks, that would be really helpful. It will likely involve some doubly-nested (or deeper) for
or while
loop.
I'm having a hard time building a minimal reproducible case. @erictraut is there any debug / verbose output I can enable to help you track this down?
You could try the --verbose
command-line option.
If you're using the language server version of pyright, you could try setting python.analysis.logLevel
to "Trace" and python.analysis.logTypeEvaluationTime
to true.
I think I've fixed this problem. I still haven't been able to repro it, so I can't say for sure. Nor can I add a test case to test it. So if you find a repro case, that would still be helpful.
The pyright test fails currently for all of our PRs, this might be the same bug, but I'm not totally sure. But maybe this can help you to reproduce it? https://github.com/ourownstory/neural_prophet/pull/1356
@leoniewgnr, thanks for the repro! That allowed me to understand the source of the bug and fix it.
So happy I could help!! Thanks for fixing it!😄
This is addressed in pyright 1.1.316, which I just published. It will also be included in this week's insiders build of pylance.
Describe the bug pyright 1.1.315 crashes from the command line with the below error when run against my codebase, while 1.1.314 runs successfully.