New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot read properties of undefined (reading 'getModelColumnOfViewPosition') #200117
Comments
Does this reproduce in the latest VS Code insiders build with all extensions disabled? If it does, please share the file which causes this |
I just experienced this while doing a first test with Github Copilot inline chat refactorisation
This was repetable. Interestingly, when I only selected the first 10 LOC it worked as expected.
|
Please share the TS code and copilot prompt you used |
I have experienced the same error under the same circumstances as mjbvz |
I recently ran into the same issue when asking Copilot to write a simple ETL script using TS and Node 20. Didn't resolve even when I disabled all other extensions. There's nothing in logs other than successful Prompt
Copilot
Environment
Feature Flags
Node setup
Network Configuration
Reachability
VS Code Configuration
Extensions
|
Same issue here. Only happens when I select all lines in a file and use CTRL + I to request an edit. |
Same issue here. What's strange is that the prompt worked fine for another file, that uses the same structure overall. Cannot share the prompt publicly as it uses some information from a database. |
If this happens to anyone just restart the application it solves it everytime it appears for me |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
2nd time I got the error
Cannot read properties of undefined (reading 'getModelColumnOfViewPosition')
has only happened twice
both times it was when I ctrl+A ctrl+X all the code in a
.tmLanguage.json
fileWindows 11 x64 zip installation
VSCode 1.8.4 stable
related: #97449
The text was updated successfully, but these errors were encountered: