Pass 3 of 3 · Deep dive of PHAROSPass 1 · OverviewPass 2 · How it works
Code Observatory / Index
Call graph
Resolves a call only when one target is defensible.
Recorded run
PHAROS at 975a38dMIT license
How it works
A name resolves within its own file first, then through imports, then if it is unique in the repository. A wrong edge misleads an assistant; a missing one only loses recall.
Indexing this commit resolved 6,977 calls and left 17,764 unresolved and 2,888 ambiguous.
Recorded runs through it
Source evidence
- Resolve calls conservatively
backend/app/codeintel/graph.py:144–244Same file, then import, then a name unique in the repository. Anything ambiguous stays unlinked. - Match a name
backend/app/codeintel/symbols.py:13–36Plain name matching in SQL. Scope applies only when repository ids are passed. - Read the neighbours
backend/app/codeintel/symbols.py:39–62Loads edges in both directions and keeps each resolution. A limit caps the rows read.
Claims this supports
Call/import graph resolution is conservative; ambiguous calls remain unresolved.
Indexing PHAROS at commit 975a38d resolved 6,977 calls and left 17,764 unresolved and 2,888 ambiguous.
Most unresolved calls reach the standard library or dependencies. PHAROS leaves them unlinked by design.
In a recorded run at commit 975a38d, find_symbol resolved _resolve_one to one definition with four callees and one caller.
One symbol chosen by the author. The graph holds resolved edges only.
