redhat-developer / redhat-developer/vscode-microprofile

workspace/symbol fails with "defines 1 params but received none" for microprofile/java/workspaceLabels in 0.18.0

Open
#630 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
21
Forks
17
Avg merge
23h 47m
Merged PRs (30d)
3

Description

Hi,

starting a workspace symbol search (e.g. Cmd/Ctrl+T "Go to Symbol in Workspace") triggers a workspace/symbol request on every keystroke. In v0.18.0, this fails consistently with:

[Error - 14:17:13] Request workspace/symbol failed.
Message: Request microprofile/java/workspaceLabels defines 1 params but received none.
Code: -32602

This does not happen on v0.17.0, where the extension logs a clean startup and searches work without error.

Steps to reproduce
  1. Install redhat.vscode-microprofile 0.18.0 alongside redhat.java (tested with 1.55.0)
  2. Open a Java/Quarkus/MicroProfile project
  3. Open "Go to Symbol in Workspace" (Cmd/Ctrl+T) and start typing a class name
  4. Observe repeated errors in the "Tools for MicroProfile" output channel, one per keystroke
Expected behavior

No error; workspace symbol search works as it did in 0.17.0.

Actual behavior

Every workspace/symbol request fails with error code -32602 ("defines 1 params but received none") for the microprofile/java/workspaceLabels request.

Environment
  • vscode-microprofile: 0.18.0 (0.18.0-20260824-1310) — regression not present in 0.17.0
  • redhat.java (Language Support for Java): 1.55.0
  • OS: macOS (darwin-arm64)
Workaround

Downgrading redhat.vscode-microprofile back to 0.17.0 resolves the issue.

Log excerpt
Aug. 28, 2026 2:14:56 PM org.eclipse.lsp4mp.ls.MicroProfileLanguageServer initialize
INFORMATION: Initializing MicroProfile server 0.18.0-20260824-1310 with .../redhat.java-1.55.0-darwin-arm64/jre/21.0.11-macosx-aarch64
[Error - 14:15:18] Request workspace/symbol failed.
Message: Request microprofile/java/workspaceLabels defines 1 params but received none.
Code: -32602

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure by running the 0.18.0 extension with redhat.java 1.55.0 and searching with Cmd/Ctrl+T. Start by tracing the workspace/symbol request and the microprofile/java/workspaceLabels interaction, comparing behavior with 0.17.0. Done means workspace symbol searches complete without repeated -32602 errors in the Tools for MicroProfile output channel.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.