Heejae Chang

I see. then `ctrl+.` must doing new `code action request` but existing `lightbulb` is using cached info. just looked through LSP spec on code action -https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_codeAction - but couldn't find...

> "125 files to be analysed" internally, each cell is treated as a file, that implementation detail might be leaking out in status bar. we might want to change the...

not sure on top of my head why this could be happening. we might be failed to create types to inject for fixture completion. or failed to inject correct import...

you need to use `python.analysis.packageIndexDepths`. see https://github.com/microsoft/pylance-release/blob/main/README.md#settings-and-customization for more detail. due to perf reason, we only index top level symbols by default. Just remember, the deeper you go (more submodules),...

I see. then if you can share repro steps or at least `trace` log, it would give us some data to take a look. repro step would be best, if...

it is a dup of https://github.com/microsoft/pylance-release/issues/5434 currently it is by design. we don't consider alias (import `x` or from y import `x`) in user files (ones you refer as `local...

@irm-codebase it looks like I misunderstood your issue. so you are asking about `unresolve import` not `add import` code action?

I tried your scenario on both `windows`, `WSL`, 'Linux` and all worked for me. I guess we need to improve our logging to see what is going on.

I added new logging for this case. it will be included in our next pre-release. we probably need that log (unless we can repro it) to figure out what is...

expand var seems not escaping user provided string.