OpenLiberty / OpenLiberty/liberty-tools-eclipse
Slow response when stop is issued during early startup
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 16
- Forks
- 20
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 16
Description
Is the purpose of 'stop' is to stop cleanly with the 'q' rather than Ctrl+C ? Or is the purpose just to stop as quickly as possible?
E.g. from a regular terminal, 'q' is quicker than Ctrl+C..since for the latter, I need to hit 'Y' to another prompt (are you sure you want to cancel).
On my windows shell at least I get:
INFO: Server defaultServer stopped.
Terminate batch job (Y/N)?
However.. I can only issue 'q' once dev mode reaches the point where it's listening for this. With Ctrl+C, OTOH, I can cancel at any time.. even "early" before dev mode is listening.
Would there be any value in implementing "stop" more like Ctrl+C plus answering 'Y'? Something to think about.
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 dev mode in a Windows shell and compare issuing 'q' once the server is listening with Ctrl+C during early startup. Trace the existing stop and startup entry points to determine the intended behavior; done should include a decided, consistently responsive stop path and coverage for early-startup cancellation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100