Erik De Bonte

@roshanjrajan-zip, I believe you are using pyright-python? Have you tried using the newish [`PYRIGHT_PYTHON_PYLANCE_VERSION` option](https://github.com/RobertCraigie/pyright-python?tab=readme-ov-file#keeping-pyright-and-pylance-in-sync)?

This issue has been closed because it needs more information and has not had recent activity. If the issue still persists, please reopen with the information requested. Thanks.

Duplicate of https://github.com/microsoft/pylance-release/issues/4846?

@flyforward2016, if you believed you were seeing this issue in 2023.10.52 and it went away in 2023.10.53, what you were actually hitting was #5009. Although the code at the core...

@git-afsantos, I think you're hitting a different issue. The original poster's log above does not contain an error about `AssignProcessToJobObject`. Please see https://github.com/microsoft/pylance-release/issues/5055 instead.

@mayankj, I wasn't sure if `utils` was a directory within your workspace or a package in your environment, so I tried it both ways. I know it's been a while...

Thanks for confirming. I'm resolving this as a duplicate of #5159.

> i made my own fork which fixes it... But this is a fork of Pyright, not Pylance, so I don't see how it could address the request to allow...

> in my experience i'm not really missing out on much by using pyright on its own instead of pylance. Really? Semantic highlighting, indexing, IntelliCode, notebook support, folding, inlay hints,...

@heejaechang, I think this is because of the following check in `SymbolIndexer.collectSymbolIndexData`: ```typescript if (DeclarationType.Alias === declaration.type) { if (!options.indexingForAutoImportMode) { // We don't include import alias for workspace files....