redhat-developer / redhat-developer/vscode-openshift-tools
Report actual status when running Debug command for component
Open
Nobody has claimed this yet.
kind/enhancement
priority/major
- Dominant language
- TypeScript
- Stars
- 123
- Forks
- 63
- Avg merge
- 6h 16m
- Merged PRs (30d)
- 74
Description
In relation to #2229. There is no way to understand what has failed. Debug command goes through three steps:
- pushing component in debug mode
- running debug port-forward and capture local port from port mapping printed into standard output
- starting nodejs debugger usin localhost:port, where port is identified on step 2
All those steps should be visible in notification with progress, so we can identify where exactly debug command failed.
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 at the Debug command and trace its three described steps: pushing the component, running port-forwarding, and starting the Node.js debugger. Add visible progress notifications for each step and verify that a failure identifies the step where it occurred.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, node.js, typescript, vscode
- Domain
- cloud, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100