-
Notifications
You must be signed in to change notification settings - Fork 3.6k
High-confidence import_map collides on common method names #2127
Copy link
Copy link
Open
Labels
bugSomething isn't workingSomething isn't workingparsing/qualityGraph extraction bugs, false positives, missing edgesGraph extraction bugs, false positives, missing edgespriority/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.Needs near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.
Description
Activity
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingparsing/qualityGraph extraction bugs, false positives, missing edgesGraph extraction bugs, false positives, missing edgespriority/highNeeds near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.Needs near-term maintainer attention; high-impact bug, regression, safety issue, or release blocker.
Severity: medium-high — survives a
confidence >= 0.9filter.from unittest.mock import patchis bound to a REST view's HTTP handlerPkgConfigView.patchwithstrategy=import_map, confidence=0.95. This is 4 of the5 misses in the filtered sample — i.e. the dominant residual error once consumers
do filter correctly.
Ask: when a name is imported in the caller's file, prefer that import's target
over a same-named method elsewhere in the graph.
Observed on v0.10.8 (build
996bad5fe6fb), macOS arm64, Python monorepo (~36k nodes / ~179k edges). Happy to provide a minimal reproduction repo if useful.