Live Share debugging not working for client
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the issue with VS Code 1.43.1, the listed Java extensions, and the setting liveshare.allowGuestDebugControl. Run a Java main program through the VS Code Run launcher during a Live Share session, then compare the server and client debugging UI. Done means the client sees the debugging toolbar and highlighted breakpoint and can control execution.
Written by the indexing model from the issue text.
Description
Hi !
I've noticed that we can't share debugging with clients during a live share session.
I'm using the latest version of Vs Code 1.43.1
Here is the vs code extensions I use :
- Language Support for Java(TM) by Red Hat
- Debugger for JavaPreview
- Live Share Extension PackPreview : with setting
"liveshare.allowGuestDebugControl": true
How to reproduce :
- start a live share session
- invite someone (a "client")
- the client set a breakpoint in the code
- the client launch the Java main program with
Runlauncher from Vs Code
What I see :
- the debug is correctly started on my station (the server)
- I see the execution stopped on the breakpoint (the line is coloured)
- The client don't see the debugging toolbar and the coloured line
What I expect :
- the client has access to the debug toolbar
- the client can control the debugging
Thanks !
- Dominant language
- Java
- Stars
- 409
- Forks
- 204
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 4
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.
More from microsoft/java-debug
-
ai-triaged bug
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/java-debug#611 · 2 comments ·
-
ai-triaged enhancement
Difficulty 4/5 3-5 days Newbie friendliness 35/100
microsoft/java-debug#608 · 3 comments ·
-
ai-triaged question
Difficulty 5/5 Over a week Newbie friendliness 30/100
microsoft/java-debug#597 · 1 comment ·
-
ai-triaged bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/java-debug#588 · 1 comment ·
-
ai-triaged question
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
microsoft/java-debug#582 · 1 comment ·
All issues in microsoft/java-debug
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
enhancement Tools
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
apache/rocketmq-dashboard#5008 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
DETECT_PARAMETER_NAMES=false silently disables @ConstructorProperties-based Creator detection too Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FasterXML/jackson-databind#6229 ·