Request textDocument/hover failed
See original GitHub issue[Error - 10:19:24] Request textDocument/hover failed.
Message: Request textDocument/hover failed with message: Invalid regular expression: /.*{1,255}/: Nothing to repeat
Code: -32603
Likely commit: https://github.com/aws-cloudformation/cfn-lint-visual-studio-code/commit/3c39873a395e24bd3f23e1ac29337c806813353a
Issue Analytics
- State:
- Created 9 months ago
- Reactions:1
- Comments:15 (6 by maintainers)
Top Results From Across the Web
Request textDocument/hover failed. On VSCode · Issue #47736
This error is happaning to me on VsCode: Notification: A request has failed. See the output for more information.
Read more >flutter - viewing .pub-cache files gives Request textDocument ...
... but after tracing a lot, the origin of the error , which was keeps on generating, whenever i hover, or clicked any...
Read more >VS Code rust-analyzer: Request textDocument/inlayHint failed
Hello everyone, today I encountered an annoying bug with rust-analyzer. I cloned RustCrypto's AEAD repo and opened it in VS Code, ...
Read more >Language Server Extension Guide - Visual Studio Code
Hover : provides hover information for a symbol selected in a text document. Signature Help: provides signature help for a symbol selected in...
Read more >Language Server Protocol Specification - 3.15
A request message to describe a request between the client and the server. ... Capabilities specific to the `textDocument/hover` request. */ hover?:
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
e.startsWith
seems to be part of parsing enums in the schema files. There was an issue in the1.0.9
version ofyaml-language-server
with number based enums. I’m going to update our dependencies to1.10.0
and see if that helps fixes the issue. For some reason I’m having troubles replicating the issue but trying all the options to replicateLooking into it now. I thought I was getting those filtered out.