lsp-jt.el fails to compile
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
- Domain
- devtools
Research direction
Reproduce the failure with M-x package-install and inspect lsp-jt.el, especially the warnings around lines 158-254 and the error at line 404. Trace the reported free variables, :level call, and argument mismatch, then verify that lsp-jt.el compiles without these diagnostics.
Written by the indexing model from the issue text.
Description
On M-x package-install lsp-jt.el fails to compile:
lsp-jt.el:158:34:Warning: reference to free variable ‘java-tests’
lsp-jt.el:165:55:Warning: reference to free variable ‘node’
lsp-jt.el:172:24:Warning: reference to free variable ‘item’
lsp-jt.el:174:11:Warning: reference to free variable
‘treemacs-java-tests-closed-state’
lsp-jt.el:178:4:Warning: ‘:level’ called as a function
lsp-jt.el:254:32:Warning: reference to free variable ‘java-tests-list’
lsp-jt.el:404:1:Error: Wrong number of arguments: (1 . 1), 0lsp-jt.el:158:34:Warning: reference to free variable ‘java-tests’
lsp-jt.el:165:55:Warning: reference to free variable ‘node’
lsp-jt.el:172:24:Warning: reference to free variable ‘item’
lsp-jt.el:174:11:Warning: reference to free variable
‘treemacs-java-tests-closed-state’
lsp-jt.el:178:4:Warning: ‘:level’ called as a function
lsp-jt.el:254:32:Warning: reference to free variable ‘java-tests-list’
lsp-jt.el:404:1:Error: Wrong number of arguments: (1 . 1), 0
- Dominant language
- Emacs Lisp
- Stars
- 696
- Forks
- 97
- PR merge metrics
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from emacs-lsp/lsp-java
-
dap-java discards module paths from resolveClasspath causing JPMS-modular projects fail to launchOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
All issues in emacs-lsp/lsp-java
Similar issues
-
area/config comp/cli comp/plugins duplicate P3 sweeper:risk-compatibility type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
NousResearch/hermes-agent#127405 · 2 comments ·
Maintainers usually reply within 1 day
-
area:*of bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
oapi-codegen/oapi-codegen#2593 ·
Maintainers usually reply within 1 day
-
agentic-workflows
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/rig#535 ·
-
agent-in-progress agent-research-recommend enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
codymikol/multiverse.nvim#337 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
WLAN-Pi/wlanpi-profiler#307 ·
Maintainers usually reply within 1 day