Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Restart Pylance without reload prompt once it is detected
See original GitHub issueThis shows the experience when creating a sample python dev container: https://cln.sh/KBwsUa (wait to the end of the recording…)
That I need to reload the window is not what I’d expect from a sample dev container (or in general). Since the Python extension activates on the existence of requirements.txt (see here) the language server change listener (see here is active.
It’s unclear to why we need to reload the window if there is no open file at all. Also, we should make an effort to not require a reload. For example, the TS extension can recover from language server crashes/restarts without any reload.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Looks like one of the endgame queries forgot to exclude on-testplan items for bugs. I’ll label this issue as verified just to kick it off the query.
Throwing my hat in the ring. I have adevcontainer post create command that install my reqs (poetry install) and it takes some time. By the time it is done, the pylance reload window disappeared and nothing gets done. It’s a non-starter, since I won’t be able to reload the window, and if I do, same happens, cycle repeats itself.
What is the purpose of this window reload upon installing pylance?