stacklok / stacklok/toolhive-studio
[Bug] Tool shutdown process is really sloooooow
Open
Nobody has claimed this yet.
Bug
- Dominant language
- TypeScript
- Stars
- 167
- Forks
- 24
- Avg merge
- 11h 32m
- Merged PRs (30d)
- 91
Description
Bug Description
It would be good to improve the perceived performance, or provide feedback, because it looks like the app crashes due to the length of time waiting (and that was only when 2 MCP servers were installed!)
Steps to Reproduce
No response
Expected Behavior
No response
Actual Behavior
No response
Priority
Medium
Environment
No response
Additional Context
No response
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
No files, tests, or entry points are identified in the issue. Start by locating the tool shutdown path and reproducing the delay with two MCP servers; done means shutdown provides clear progress or feedback and no longer appears to have crashed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100