Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`lsp-jt-run` not works

Open
  • Is something wrong?
#454 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
emacs-lisp, java
Domain
devtools, testing

Research direction

Start at the lsp-jt-run command and reproduce the reported wrong-type-argument hash-table-p nil error using the provided workspace/executeCommand trace. Determine why the vscode.java.test.junit.argument response is nil; done means the selected Java test runs successfully through the command.

Written by the indexing model from the issue text.

Description

Describe the bug
lsp-jt-run not works

Note
My environment Apple m2 pro, macOS 13.5.2 (22G91)
Emacs version is Emacs-plus 28 with-native-comp

To Reproduce
Try to execute command by key x or direct on M-x
and it returns message (wrong-type-argument hash-talbe-p nil)

Expected behavior
Test is run

Logs
Please include the debug stack trace (if there is an error) and the content of Messages buffer with lsp-print-io set to t in case the bug is related to client->server communication.
This is my lsp session

 |     |-[-] executeCommandProvider:
 |     |  `-[X] commands: [vscode.java.checkProjectSettings vscode.java.isOnClasspath java.project.list vscode.java.fetchUsageData 
java.navigate.openTypeHierarchy vscode.java.test.search.items.all java.edit.handlePasteEvent sts.java.hierarchy.supertypes 
java.edit.stringFormatting sts.java.hierarchy.subtypes vscode.java.resolveMainClass vscode.java.test.search.location 
vscode.java.buildWorkspace vscode.java.resolveJavaExecutable sts.java.type java.project.refreshDiagnostics 
vscode.java.resolveInlineVariables java.project.listSourcePaths sts.java.search.packages java.project.getClasspaths 
java.project.updateSourceAttachment vscode.java.resolveClasspath vscode.java.resolveBuildFiles java.decompile 
vscode.java.resolveSourceUri vscode.java.test.search.items vscode.java.fetchPlatformSettings 
java.project.resolveSourceAttachment sts.java.removeClasspathListener java.project.addToSourcePath 
java.completion.onDidSelect vscode.java.startDebugSession java.project.import vscode.java.validateLaunchConfig 
java.project.resolveStackTraceLocation vscode.java.test.junit.argument vscode.java.resolveMainMethod java.project.getSettings 
java.project.resolveWorkspaceSymbol sts.java.addClasspathListener java.project.upgradeGradle java.project.createModuleInfo 
vscode.java.test.get.testpath java.resolvePath sts.java.javadoc vscode.java.resolveElementAtSelection 
vscode.java.test.search.codelens java.edit.organizeImports java.project.removeFromSourcePath sts.java.javadocHoverLink 
java.project.getAll java.reloadBundles java.project.isTestFile sts.java.search.types vscode.java.resolveClassFilters 
java.getPackageData java.navigate.resolveTypeHierarchy vscode.java.updateDebugSettings sts.java.location 
java.protobuf.generateSources vscode.java.inferLaunchCommandLength]

[Trace - 12:53:31 PM] Sending request 'workspace/executeCommand - (251)'.
Params: {
  "command": "vscode.java.test.junit.argument",
  "arguments": [
    "{\"classFullName\":\"my.lazyskulptor.commerce.repo.TxManagerTest\",\"scope\":4,\"testName\":\"verifyCommitIsCalled\",\"testKind\":1,\"project\":\"webflux-template-hb\",\"uri\":\"file:///Users/hyeonjunpark/Workspace/personal/webflux-template/src/test/java/my/lazyskulptor/commerce/repo/TxManagerTest.java\",\"start\":{\"line\":31,\"character\":9},\"end\":{\"line\":31,\"character\":29}}"
  ]
}


[Trace - 12:53:31 PM] Received response 'workspace/executeCommand - (251)' in 40ms.
Result: null
Dominant language
Emacs Lisp
Stars
696
Forks
97
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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.

More from emacs-lsp/lsp-java

All issues in emacs-lsp/lsp-java

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.