Skip to content

Constantly Bombarded by Error Message: Request textDocument/hover failed. #907

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.

Sign up for GitHub

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

Jump to bottom
Open
lamyergeier opened this issue Jul 13, 2023 · 17 comments
Open

Constantly Bombarded by Error Message: Request textDocument/hover failed. #907

lamyergeier opened this issue Jul 13, 2023 · 17 comments
Labels
bug Something isn't working question Further information is requested

Comments

@lamyergeier
Copy link

lamyergeier commented Jul 13, 2023 •
edited
Loading

Code editor

Codium

Platform

Fedora 38

Version

v1.38.0

What do you see instead?

image

Additional information

bashIde.explainshellEndpoint is blank in the Settings

Issue started randomly from today.
@skovhus
Copy link
Collaborator

skovhus commented Jul 14, 2023

That is odd. Can you provide a code example?

@skovhus skovhus added the bug Something isn't working label Jul 14, 2023
@skovhus
Copy link
Collaborator

skovhus commented Jul 15, 2023

Can you reproduce this with the newest server version (5.0)?

@skovhus skovhus added the question Further information is requested label Jul 15, 2023
@ColorfulRhino
Copy link

ColorfulRhino commented Mar 26, 2024 •
edited
Loading

Hello! I am getting bombarded by the same error messages :(

Using: VS-Codium with Bash IDE version 1.38 (from 9 months ago, no newer version is available). It's using language server 4.10 as far as I can see from the plugin changelog. Not sure how or if I can upgrade to a newer language server without upgrading the plugin itself.
Unfortunately it is unclear if you @skovhus are the maintainer of the plugin or if it's someone else (if yes, I'm sorry for bothering you, I could not find out who is the actual maintainer).

The files I edited are for example https://github.com/armbian/build/blob/main/lib/functions/compilation/kernel-config.sh and others in the same repo.

Some of the log messages:

[...]
[Error - 8:50:36 PM] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:37 PM] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:38 PM] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:39 PM] Unhandled Rejection at promise: [object Promise], reason: RuntimeError: memory access out of bounds
    at wasm://wasm/000b627a:wasm-function[236]:0x2a422
    at Parser.parse (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/web-tree-sitter/tree-sitter.js:1:53101)
    at Analyzer.analyze (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/analyser.js:47:34)
    at BashServer.<anonymous> (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:241:45)
    at Generator.next (<anonymous>)
    at /home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:4:12)
    at BashServer.analyzeAndLintDocument (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:238:16)
    at /home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:122:22
[Error - 8:50:39 PM] Request textDocument/definition failed.
  Message: Request textDocument/definition failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:39 PM] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:39 PM] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:39 PM] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:43 PM] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:44 PM] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:45 PM] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:46 PM] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:46 PM] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:46 PM] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
  Code: -32603 
[Error - 8:50:47 PM] Unhandled Rejection at promise: [object Promise], reason: RuntimeError: memory access out of bounds
    at wasm://wasm/000b627a:wasm-function[236]:0x2a422
    at Parser.parse (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/web-tree-sitter/tree-sitter.js:1:53101)
    at Analyzer.analyze (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/analyser.js:47:34)
    at BashServer.<anonymous> (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:241:45)
    at Generator.next (<anonymous>)
    at /home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:4:12)
    at BashServer.analyzeAndLintDocument (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:238:16)
    at /home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:122:22
[Error - 8:50:47 PM] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: memory access out of bounds
  Code: -32603 
[...]

The logs start like this:

[Info  - 4:05:55 PM] 15:05:55.253 INFO BackgroundAnalysis: resolving glob "**/*@(.sh|.inc|.bash|.command)" inside "file:///home/user/build-fork"...
[Error - 4:05:55 PM] Unhandled Rejection at promise: [object Promise], reason: TypeError: Cannot read properties of undefined (reading 'apply')
    at e.<computed> (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/web-tree-sitter/tree-sitter.js:1:16465)
    at wasm://wasm/001ec906:wasm-function[21]:0x1ccf
    at e.<computed> (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/web-tree-sitter/tree-sitter.js:1:16465)
    at wasm://wasm/001ec906:wasm-function[19]:0x17aa
    at wasm://wasm/000b627a:wasm-function[234]:0x25842
    at Object.Module._ts_parser_parse_wasm (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/web-tree-sitter/tree-sitter.js:1:33493)
    at Parser.parse (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/web-tree-sitter/tree-sitter.js:1:53325)
    at Analyzer.analyze (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/analyser.js:47:34)
    at BashServer.<anonymous> (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:241:45)
    at Generator.next (<anonymous>)
[Info  - 4:05:55 PM] 15:05:55.358 INFO BackgroundAnalysis: Glob resolved with 500 files after 0.105 seconds
[Warn  - 4:05:55 PM] 15:05:55.362 WARNING ⛔️ Error while parsing file:///home/user/build-fork/compile.sh: syntax error
[Warn  - 4:05:55 PM] 15:05:55.366 WARNING ⛔️ BackgroundAnalysis: Failed analyzing file:///home/user/build-fork/extensions/armbian-live-patch.sh. Error: Cannot read properties of undefined (reading 'apply')
[Warn  - 4:05:55 PM] 15:05:55.367 WARNING ⛔️ BackgroundAnalysis: Failed analyzing file:///home/user/build-fork/extensions/bluetooth-hciattach.sh. Error: Cannot read properties of undefined (reading 'apply')
[Warn  - 4:05:55 PM] 15:05:55.368 WARNING ⛔️ BackgroundAnalysis: Failed analyzing file:///home/user/build-fork/extensions/c-plus-plus-compiler.sh. Error: Cannot read properties of undefined (reading 'apply')
[Warn  - 4:05:55 PM] 15:05:55.368 WARNING ⛔️ BackgroundAnalysis: Failed analyzing file:///home/user/build-fork/extensions/cleanup-space-final-image.sh. Error: Cannot read properties of undefined (reading 'apply')
[Warn  - 4:05:55 PM] 15:05:55.370 WARNING ⛔️ Error while parsing file:///home/user/build-fork/extensions/detect-unused-extensions.sh: syntax error
[Warn  - 4:05:55 PM] 15:05:55.375 WARNING ⛔️ BackgroundAnalysis: Failed analyzing file:///home/user/build-fork/extensions/gen-sample-extension-docs.sh. Error: Cannot read properties of undefined (reading 'apply')
[Warn  - 4:05:55 PM] 15:05:55.377 WARNING ⛔️ Error while parsing file:///home/user/build-fork/extensions/grub-riscv64.sh: syntax error
[Warn  - 4:05:55 PM] 15:05:55.380 WARNING ⛔️ BackgroundAnalysis: Failed analyzing file:///home/user/build-fork/extensions/grub.sh. Error: Cannot read properties of undefined (reading 'apply')
[...]

And also include things like this (Error while parsing file: syntax error, not sure if that's another issue or relevant for this exact issue):

[...]
[Warn  - 4:05:55 PM] 15:05:55.912 WARNING ⛔️ Error while parsing file:///home/user/build-fork/cache/sources/linux-kernel-worktree/6.6__arm64__arm64/scripts/syscallnr.sh: syntax error
[Warn  - 4:05:55 PM] 15:05:55.913 WARNING ⛔️ Error while parsing file:///home/user/build-fork/cache/sources/linux-kernel-worktree/6.6__arm64__arm64/scripts/syscalltbl.sh: syntax error
[Warn  - 4:05:55 PM] 15:05:55.927 WARNING ⛔️ Error while parsing file:///home/user/build-fork/cache/sources/linux-kernel-worktree/6.1__wsl2-x86__amd64/scripts/as-version.sh: syntax error
[Warn  - 4:05:55 PM] 15:05:55.928 WARNING ⛔️ Error while parsing file:///home/user/build-fork/cache/sources/linux-kernel-worktree/6.1__wsl2-x86__amd64/scripts/cc-version.sh: syntax error
[Warn  - 4:05:55 PM] 15:05:55.933 WARNING ⛔️ BackgroundAnalysis: Failed analyzing file:///home/user/build-fork/cache/sources/linux-kernel-worktree/6.1__wsl2-x86__amd64/scripts/decode_stacktrace.sh. Error: Cannot read properties of undefined (reading 'apply')
[Warn  - 4:05:55 PM] 15:05:55.934 WARNING ⛔️ Error while parsing file:///home/user/build-fork/cache/sources/linux-kernel-worktree/6.1__wsl2-x86__amd64/scripts/depmod.sh: syntax error
[Info  - 4:05:55 PM] 15:05:55.940 INFO BackgroundAnalysis: Completed after 0.687 seconds.
[Error - 4:06:16 PM] Unhandled Rejection at promise: [object Promise], reason: TypeError: Cannot read properties of undefined (reading 'apply')
    at e.<computed> (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/web-tree-sitter/tree-sitter.js:1:16465)
    at wasm://wasm/001ec906:wasm-function[21]:0x1ccf
    at e.<computed> (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/web-tree-sitter/tree-sitter.js:1:16465)
    at wasm://wasm/001ec906:wasm-function[19]:0x17aa
    at wasm://wasm/000b627a:wasm-function[234]:0x25842
    at Parser.parse (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/web-tree-sitter/tree-sitter.js:1:53325)
    at Analyzer.analyze (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/analyser.js:47:34)
    at BashServer.<anonymous> (/home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:241:45)
    at Generator.next (<anonymous>)
    at /home/user/.vscodium-server/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:8:71
[Warn  - 4:06:31 PM] 15:06:31.094 WARNING ⛔️ Error while parsing file:///home/user/build-fork/lib/functions/compilation/kernel-make.sh: syntax error
[Warn  - 4:06:31 PM] 15:06:31.621 WARNING ⛔️ ShellCheck: disabling linting as no executable was found at path 'shellcheck'
[...]

@corneliusroemer
Copy link

corneliusroemer commented Jul 7, 2024 •
edited
Loading

I'm getting the same bug on the latest version v1.41.0 using language server v5.2.0 on macOS VSCode 1.91

It makes the extensions fully unusable unfortunately (I love it in general!)

Code 2024-07-07 18 16 18 
[Error - 16:23:12] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
  Code: -32603 
[Error - 17:01:14] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603 
[Error - 17:01:14] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
  Code: -32603 
[Error - 17:01:14] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603 
[Error - 17:01:15] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603 
[Error - 17:01:18] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
  Code: -32603 
[Error - 17:01:18] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
  Code: -32603 
[Error - 17:01:25] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
  Code: -32603 
[Error - 17:01:29] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: memory access out of bounds
  Code: -32603 
[Error - 17:01:32] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603 
[Error - 17:01:39] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
  Code: -32603 
[Error - 18:13:47] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
  Code: -32603 
[Error - 18:13:47] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: memory access out of bounds
  Code: -32603 
[Error - 18:13:48] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
  Code: -32603
...

@ColorfulRhino
Copy link

latest version v1.41.0 using language server v5.2.0 on macOS VSCode 1.91

You're lucky, the version on https://open-vsx.org/extension/mads-hartmann/bash-ide-vscode is still stuck on 1.38.0

@mwinters-stuff
Copy link

I am getting the same errors, using "latest" v1.41.0, also with the same errors as above..

The project, has quite a lot of scripts (617), which "all" seem to be scanned even when "never" opened...

@schrummy14
Copy link

I have also begun to get these "memory access out of bounds" messages when working with shell scripts.
Using server v1.41.0 on Fedora 40.

@SplitGemini
Copy link

+1

@lamyergeier
Copy link
Author

lamyergeier commented Sep 17, 2024 •
edited
Loading

@skovhus Again facing it today

image

@gissf1
Copy link

gissf1 commented Sep 25, 2024

I'm also getting these errors rather frequently, but its been happening for 6 months or longer. I don't think it's platform specific, but I'm on Arch Linux with VS-codium v1.92.2-24228 and Bash IDE v1.38.0. I use many shell scripts in my various projects, so this plugin is generally of great help to my day.

This issue seems to get triggered when there is a syntax error in the script (like if you make an "if" without a matching "fi" or mismatched parenthesis / curly braces), then move your cursor around the script in random places. I'll try to be more mindful of a pattern that triggers it and report back if I discover specific steps to consistently reproduce the issue.

As a workaround, I sometimes disable and re-enable the plugin, or if that fails, often restarting the IDE helps.

@skovhus
Copy link
Collaborator

skovhus commented Sep 25, 2024

I'll try to be more mindful of a pattern that triggers it and report back if I discover specific steps to consistently reproduce the issue.

That would be great. Having a hard time reproducing this.

@gissf1
Copy link

gissf1 commented Sep 25, 2024

OK, it just triggered again for me. Not quite a reproducer, but I seem to at least have a backtrace.

I got these error messages on the console (I just SNIPed my home directory path from the messages):

[Error - 2:50:48 PM] Unhandled Rejection at promise: [object Promise], reason: RuntimeError: memory access out of bounds
    at wasm://wasm/000b627a:wasm-function[236]:0x2a422
    at Parser.parse (SNIP/.vscode-oss/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/web-tree-sitter/tree-sitter.js:1:53101)
    at Analyzer.analyze (SNIP/.vscode-oss/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/analyser.js:47:34)
    at BashServer.<anonymous> (SNIP/.vscode-oss/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:241:45)
    at Generator.next (<anonymous>)
    at SNIP/.vscode-oss/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:8:71
    at new Promise (<anonymous>)
    at __awaiter (SNIP/.vscode-oss/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:4:12)
    at BashServer.analyzeAndLintDocument (SNIP/.vscode-oss/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:238:16)
    at SNIP/.vscode-oss/extensions/mads-hartmann.bash-ide-vscode-1.38.0-universal/node_modules/bash-language-server/out/server.js:122:22
[Error - 2:50:48 PM] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: memory access out of bounds
  Code: -32603 
[Error - 2:50:48 PM] Request textDocument/documentSymbol failed.
  Message: Request textDocument/documentSymbol failed with message: memory access out of bounds
  Code: -32603 
[Error - 2:50:48 PM] Request textDocument/documentHighlight failed.
  Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
  Code: -32603 
[Error - 2:51:53 PM] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603 
[Error - 2:51:53 PM] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: memory access out of bounds
  Code: -32603

I was typing this line within a shell script function on line 584:

	DB_PASSWORDS=$( echo -e "$DB_PASSWORDS" | sed -r 's///g' )

I had typed the line and moved my text cursor back with the arrow keys to the s///g regex part between the first and second slash, intending to fill it in.

After it triggers, the problem happens almost continuously just by moving the mouse cursor over the code text. I assume it's looking for some tooltip text to pop up and failing to get that due to some inconsistent internal state.

Disabling the plugin, restarting plugins, and then reenabling it restored normal operation.

Backspacing the line from the end and re-typing it did not re-trigger the issue.

Getting it to happen from a fresh start is not so easy. Seems to happen most often after I've been working for a while.

I'll report back again if I find anything else.

@skovhus skovhus mentioned this issue Sep 25, 2024
Merged
@skovhus
Copy link
Collaborator

skovhus commented Sep 26, 2024

The stack-trace indicates that it could be an issue with treesitter. I just upgraded to the latest version, and released a new LSP version 5.4.2 and vscode extension 1.43. Let me know if it fixes anything.

@gissf1
Copy link

gissf1 commented Sep 26, 2024

latest version v1.41.0 using language server v5.2.0 on macOS VSCode 1.91

You're lucky, the version on https://open-vsx.org/extension/mads-hartmann/bash-ide-vscode is still stuck on 1.38.0

For what it's worth, the updated plugin isn't showing for me in VS Codium either.

According to the open-vsx website, 1.38.0 is still the latest: https://open-vsx.org/extension/mads-hartmann/bash-ide-vscode

I see 1.43 here: https://marketplace.visualstudio.com/items?itemName=mads-hartmann.bash-ide-vscode but that isn't very easy to install in VS Codium.

@skovhus Any chance you could update on open-vsx too? Or are they just slow to update their listed versions?

In the meantime, I'm trying a workaround to install v1.43.0, and I'll report back if I can provide more feedback on this issue.

@gissf1
Copy link

gissf1 commented Oct 16, 2024 •
edited
Loading

ok, coming back to this...

I was able to get v1.43 installed in VS Codium via the VSIX Manager plugin, (available here: https://open-vsx.org/extension/zokugun/vsix-manager).

@skovhus Thus far, over the course of a few weeks, I have not had a single crash or error message since installing this update. So from that perspective, I think this issue may be fixed in v1.43!

That said, it would be nice if this updated release were available in the open-vsx marketplace as well, since they currently only provide access to v1.38 and older releases. Anyone using these older versions are likely to find their way to this bug report when they encounter the issue. The open-vsx page for the extension (the open-vsx.org URL linked in my last post) says it has no owner, and requests that someone claim it. I imagine anyone using a variant of VS Code that isn't a Microsoft release version would be using the open-vsx marketplace rather than the official VS Code marketplace.

For more information on claiming the plugin, I found this link: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions

Thanks for the help, and hopefully my reply here can help others as well!

@ColorfulRhino since you were also on the same version 1.38 that I was on, consider checking out the VSIX Manager plugin or manually downloading and installing the VSIX plugin from MS VS store to update your plugin if you haven't already.

@CJ-Abrams
Copy link

For whoever is still having the same issue with the latest BashIDE VSCode extension (v1.43), a partial workaround could be to use an extension like reload, from https://marketplace.visualstudio.com/items?itemName=natqe.reload (source at https://github.com/natqe/reload), which allows fast-reloading of the editor and all installed extensions, without having to manually quit and restart it completely, keeping the main UI opened and restoring all opened tabs and files in their last state before reloading.

So as soon as the discussed error re-occurs, just click the reload button on the bottom-right corner, and you will be able to continue working after a few seconds.

Note: Extension tested and still working in latest VSCode/VSCodium version (v1.97.0 at the time of writing).

@toby5box
Copy link

I'm getting spammed by this error, which is unfortunate since I only installed Bash IDE to try today.

Version

1.43.0
Last Updated
2025-02-24, 20:51:02

VS Code

Version: 1.97.2
Commit: e54c774e0add60467559eb0d1e229c6452cf8447
Date: 2025-02-12T23:20:35.343Z (1 wk ago)
Electron: 32.2.7
ElectronBuildId: 10982180
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Darwin x64 23.6.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working question Further information is requested
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
10 participants
@skovhus @mwinters-stuff @toby5box @gissf1 @corneliusroemer @schrummy14 @SplitGemini @lamyergeier @CJ-Abrams @ColorfulRhino