-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
[BUG] Request textDocument/documentSymbol failed. #377
Comments
I cannot reproduce this behavior. What do you mean with CucumberFormat? Maybe you can give some examples? |
And some information about your environment would be good, like VSCode Version, Python Version and Robot Framework Version. |
I am seeing the same errors. VSCode version: 1.96.2 |
Again, I cannot reproduce this bug. It would be really helpfull, if you can provide more informations. when exactly does this error occur? |
when exactly does this error occur? When switching between .robot files
Edit: |
Thanks for the example, but I still cannot reproduce it. |
I’ve uploaded a new version; could you try it out and give me some feedback? |
I just tried it and it seems to have solved the issue. Thanks! |
Hi, I see two different errors types mentioned:
On my side with the new version (RobotCode cache cleared and server restart), il still have the second one. The error occurs when I modify a variable in my Settings.json and save the file:
[Error - 10:01:09 AM] Sending notification workspace/didChangeConfiguration failed Thanks ! |
I can confirm that the issue for the reported error "Request textDocument/documentSymbol failed" is fixed with 0.106.0 - thanks a lot 👍 UPDATE @d-biehl:
|
The |
This issue has been automatically closed due to a commit message. I believe I have fixed the issues related to this error message. If the problem persists, please feel free to reopen the issue! |
Rejoiced too soon.. After updating to 0.106.0 I did not encounter the issue, but for some reason, the error appeared again with 0.106.0:
(I don't have permissions to reopen the ticket.) |
@d-biehl |
For me the issue is unfortunately not fixed with version 0.108.0 and the error notification in VS code saying "Request textDocument/documentSymbol failed" still pops up when a .resource or .robot file is opened in a VS Code tab. This is the output:
What I found out: I can only reproduce the behaviour with the following conditions:
As soon as I delete the .robotidy configuration or comment out its content, clear the cache of RobotCode and restart VS Code, the problem is gone. |
@Weinzierleiner what is in your |
@d-biehl I investigated a little more. Here are my conclusions:
I was just able to reproduce it more accurately - here are the steps:
With having |
Describe the bug
I have the plugin installed and some RobotFramework test files in CucumberFormat open.
I'm working under Windows 11.
Steps To Reproduce
Logs
[Error - 09:58:28] Request textDocument/documentSymbol failed.
TypeError: Cannot read properties of undefined (reading 'range')
at hn (c:\Users\P034724.vscode\extensions\d-biehl.robotcode-0.105.0\out\extension.js:35:71898)
at s (c:\Users\P034724.vscode\extensions\d-biehl.robotcode-0.105.0\out\extension.js:35:46654)
at Object.yD [as map] (c:\Users\P034724.vscode\extensions\d-biehl.robotcode-0.105.0\out\extension.js:35:46740)
at Object.jn [as asSymbolInformations] (c:\Users\P034724.vscode\extensions\d-biehl.robotcode-0.105.0\out\extension.js:35:71541)
at c (c:\Users\P034724.vscode\extensions\d-biehl.robotcode-0.105.0\out\extension.js:39:56109)
at async uI.provideDocumentSymbols (file:///c:/Program%20Files/Microsoft%20VS%20Code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:138:126457)
Start analyzing workspace for 4 documents
End analyzing workspace for 4 documents took 0.0160 seconds
Start collect workspace diagnostic for 4 documents
End collect workspace diagnostic for 4 documents took 0.2030 seconds
Start analyzing workspace for 4 documents
End analyzing workspace for 4 documents took 0.0000 seconds
Start collect workspace diagnostic for 4 documents
End collect workspace diagnostic for 4 documents took 0.2030 seconds
The text was updated successfully, but these errors were encountered: