`pyright` type checking is very slow

Open

#8,563 opened on Sep 18, 2026 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 52/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Active
Tech stack: python
Domain: developer-experience, performance

Research direction

Start by reproducing the issue with the test.py example and pyright --outputjson, comparing results with and without show_graph_report(1, 2). Trace the binaryninja.interaction.show_graph_report API and its exposed type information to identify what causes the evaluation slowdown. Done means importing and using it no longer causes the reported drastic increase in pyright time.

Written by the indexing model from the issue text.

Description

Version and Platform (required):

Binary Ninja Version: 6.0.10601 (can't easily test dev for packaging reasons)
Edition: Personal
OS: NixOS
OS Version: 26.05
CPU Architecture: x64

Bug Description:
Importing and using binaryninja.interaction.show_graph_report causes pyright evaluation time to rise from 6s to ~40s.

Steps To Reproduce:

Create test.py
Paste:

from binaryninja.interaction import show_graph_report
show_graph_report(1, 2)

Run pyright --outputjson test.py
Observe timeInSec to be vastly larger than normal (~40s for my system)
Comment out show_graph_report(1, 2)
Rerun pyright and observe timeInSec of below 1s

Expected Behavior:
Importing show_graph_report should not cause a drastic increase in pyright evaluation time.

Screenshots/Video Recording:
~~If applicable, please add screenshots/video recording here to help explain your problem.~~

Binary:
~~If applicable, please provide us with the binary to help us work with the issue faster. Here are a few options:~~

Additional Information:
I'm using this to get pyright to discover the api in my dev env:

BINJA_ROOT=$(cat "$HOME/.binaryninja/lastrun" | tr -d '\n')
export PYTHONPATH="$BINJA_ROOT/python:$PYTHONPATH"

Dominant language: C++
Stars: 1.3k
Forks: 298
Avg merge: 4d 13h
Merged PRs (30d): 20

Contributor guide

No contributing guide indexed for this repository

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

rate_limit_sni_expiry AuTest is flaky: the holder races FIFO removal Open

AuTest Bug Tests

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

apache/trafficserver#13714 · Opened Sep 22, 2026
[CI] Nightly Clang build broken: ToJsonFunction no longer binds to registerFunction Open

bug build

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

facebookincubator/velox#19143 · Opened Sep 22, 2026
Misc. bug: Vulkan: ggml_backend_vk_get_device_memory reports free > total when the driver's heapBudget exceeds heap size (Intel iGPU, Windows); downstream consumers underflow Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

ggml-org/llama.cpp#29277 · Opened Sep 22, 2026
tt_metal/hw/inc/internal/tt-2xx/quasar/overlay/xcustom_test.hpp needs reimplementing Open

Difficulty 2/5 1-3 hours Newbie friendliness 68/100

tenstorrent/tt-metal#57393 · 1 comment · Opened Sep 22, 2026
Ford-Fulkerson entry point sizes the graph by argument count, not by vertex id range, so it crashes on any vertex id >= args.length Open

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

objectionary/eo-graphs#74 · Opened Sep 22, 2026

More C++ issues