-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Labels
priority/P1High priority issueHigh priority issue
Description
What happened?
Whatever command associate with running a node file. For example
npm run dev
node server.js
will cause the CLI to run very long time without any response, possibly stuck over there.
If I click Ctrl + C. It will quit with node running response. But it seems the CLI is unable to detect problems and stop at a place when it see any problems
What did you expect to happen?
It should be running properly without any problem.
Client information
Client Information
Run qwen to enter the interactive CLI, then run the /about command.
$ qwen /about
# paste output hereLogin information
No response
Anything else we need to know?
No response
Sub-issues
Metadata
Metadata
Assignees
Labels
priority/P1High priority issueHigh priority issue