Andrew Gallant c548ef2027 [ty] Squash false positive logs for failing to find builtins as a real module ... I recently started noticing this showing up in the logs for every scope based completion request: ``` 2025-12-11 11:25:35.704329935 DEBUG request{id=29 method="textDocument/completion"}:map_stub_definition: Module `builtins` not found while looking in parent dirs ``` And in particular, it was repeated several times. This was confusing to me because, well, of course `builtins` should resolve. This particular code path comes from looking for the docstrings of completion items. This involves a spelunking that ultimately tries to resolve a "real" module if the stub doesn't have available docstrings. But I guess there is no "real" `builtins` module, so `resolve_real_module` fails. Which is fine, but the noisy logs were annoying since this is an expected case. So here, we carve out a short circuit for `builtins` and also improve the log message.		2025-12-11 12:50:08 -05:00
..
resources	[ty] Uniformly use "not supported" in diagnostics (#21916)	2025-12-11 15:03:55 +00:00
src	[ty] Squash false positive logs for failing to find builtins as a real module	2025-12-11 12:50:08 -05:00
tests	[ty] Don't send publish diagnostics for clients supporting pull diagnostics (#21772)	2025-12-04 08:12:04 +01:00
build.rs
Cargo.toml	[ty] bump dependencies to pull in Salsa support for ordermap (#21854)	2025-12-09 19:08:03 -08:00
mdtest.py	[ty] mdtests with external dependencies (#20904)	2025-12-08 11:44:20 +01:00
mdtest.py.lock