eclipse-wildwebdeveloper / eclipse-wildwebdeveloper/wildwebdeveloper
Error in starting "Chrome Debug"
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 201
- Forks
- 76
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 21
Description
Hi Team
I started my node app in debug mode.
Debugger listening on ws://127.0.0.1:9222/6aa910ac-e441-477c-83ee-ec51045b86af
But when i connect my eclipse to the debugger, using "Chrome Debug" i got an error "Unknown Exception
"
To client: {"seq":0,"type":"response","request_seq":2,"command":"launch","success":false,"message":"Cannot connect to runtime process, timeout after 10000 ms - (reason: Can't find a valid target that matches: undefined. Available pages: ["file:///server/server.js"]).","body":{"error":{"id":2010,"format":"Cannot connect to runtime process, timeout after {_timeout} ms - (reason: {_error}).","variables":{"_error":"Can't find a valid target that matches: undefined. Available pages: ["file:////server/server.js"]","_timeout":"10000"}}}}
Kindly help me in resolving this.
Contributor guide
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 reproducing issue 696 with the Node app entry point server/server.js and the reported ws://127.0.0.1:9222 debugger endpoint. Inspect how Eclipse's Chrome Debug launch handles the available file:///server/server.js page and target selection; done means the debugger connects without the 10-second timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, node.js
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100