microsoft / microsoft/java-debug
runInTerminal reverse-request missing cwd key
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 409
- Forks
- 204
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 4
Description
According to the DAP specification, the cwd key in the runInTerminal request is mandatory.
https://microsoft.github.io/debug-adapter-protocol/specification#Reverse_Requests_RunInTerminal
however, the java debug server sends the request without this key:
2018-12-20 00:03:04,861 - DEBUG - Message received: {'command': 'runInTerminal', 'arguments': {'kind': 'integrated', 'title': 'Java Debug Console', 'args': ['/Library/Java/JavaVirtualMachines/jdk1.8.0_162.jdk/Contents/Home/jre/bin/java', '-agentlib:jdwp=transport=dt_socket,server=n,suspend=y,address=localhost:53159', '-Dfile.encoding=UTF-8', '-cp', '/Users/ben/.vim/bundle/vimspector/support/test/java/test_project/target/classes', 'com.vimspector.test.TestApplication', 'hello', 'world!']}, 'seq': 2, 'type': 'request'}
of course, clients could work around this, but it would be nice for the server to include the required parameter.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the Java debug server code that constructs the DAP runInTerminal reverse request, then compare its arguments with the linked DAP specification. The work is done when the request includes the mandatory cwd key and the relevant request behavior is covered by the project's tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100