Skip to content
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

Output panel keeps popping up #56

Open
jmbeach opened this issue Jan 23, 2023 · 6 comments
Open

Output panel keeps popping up #56

jmbeach opened this issue Jan 23, 2023 · 6 comments

Comments

@jmbeach
Copy link

jmbeach commented Jan 23, 2023

The output panel keeps popping up in the middle of typing because it runs into an error such as "Request textDocument/hover" failed. I'd really like it to stay hidden.

Seems very similar to this issue jamesbirtles/svelte-vscode#41

@MrVauxs
Copy link

MrVauxs commented May 13, 2023

It's really annoying when even hovering for a second a svelte-fa element.

[Error - 6:00:36 PM] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: EISDIR: illegal operation on a directory, read
  Code: -32603 

@paolodina
Copy link

[Error - 11:05:01 PM] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: must pass in a file:// URI to convert to a file path
  Code: -32603 

@dromzeh
Copy link

dromzeh commented Jul 14, 2023

Also getting this issue where it completely floods the panel.

TypeError: must pass in a file:// URI to convert to a file path
    at Object.fileUriToPath (c:\Users\marcel\.vscode-insiders\extensions\ardenivanov.svelte-intellisense-0.7.1\server\out\utils.js:25:15)
    at reloadDocument (c:\Users\marcel\.vscode-insiders\extensions\ardenivanov.svelte-intellisense-0.7.1\server\out\server.js:69:70)

@kevinyjiang
Copy link

Any update here?

@Carlos-err406
Copy link

also getting this, so frustrating
sad that it seems like is not going to be fixed

@dromzeh
Copy link

dromzeh commented Sep 16, 2023

sad that it seems like is not going to be fixed

Seems the maintainer is no longer active looking at his contribution graph; making a fix PR directly to this repo seems to be practically useless - unless someone ends up forking && maintaining this... I'll see if I can get a fix out to my fork if I have some spare time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants