microsoft / microsoft/pyright

Process never finishes in `1.1.405`, `1.1.406`, `1.1.407`, `1.1.408`

Open
#11,076 10 comments 0 reactions 0 assignees View on GitHub
bug regression
Dominant language
Python
Stars
15.6k
Forks
1.8k
Avg merge
12h 13m
Merged PRs (30d)
52

Description

**Describe the bug**
We have a large code base that uses a custom library which has a large, auto-generated file of pydantic models. Since `1.1.405` including all following versions we're seeing the issue that `pyright` does not finish. It will consume all of the cores it gets but simply run ad infinitum - our CI pipelines kill the job after an hour. Going back to `1.1.404` finishes in ~5 minutes.

I am willing to debug this but I have no idea where to even start looking and I can't share code.

Contributor guide

Open the contributing guide

Research direction

Start by comparing Pyright 1.1.404 with 1.1.405 on a representative large generated Pydantic-model code base. Since no reproducible code, identify a minimal reduction or profiling result that isolates the regression, then verify that analysis completes and no longer consumes all available cores indefinitely.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
performance, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.