Add timeout to ConnectionManager.stop() to prevent shutdown hang#680

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open

kisharnath wants to merge2 commits intomcp-use:main

base:main

Choose a base branch

Open

Conversation

Copy link

No description provided.

Add timeout to ConnectionManager.stop() to prevent shutdown hang

c39b67e

Copy link

Review the following changes in direct dependencies. Learn more aboutSocket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@esbuild-plugins/node-modules-polyfill@0.2.2
	@esbuild-plugins/node-globals-polyfill@0.2.3
	@types/react-dom@18.3.7
	vite@4.5.14
	react@18.3.1
	util@0.12.5
	typescript@5.9.3
	react-dom@18.3.1
	@vitejs/plugin-react@4.7.0

kisharnath mentioned this pull request

Open

15 tasks

Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more aboutSocket for GitHub.

Action	Severity	Alert (click "▶" to expand/collapse)
Warn		Obfuscated code: npm`vite` is 92.0% likely obfuscated Confidence: 0.92 Location:Package overview From:libraries/typescript/packages/mcp-use/examples/client/react/package.json →`npm/vite@4.5.14` ℹ Read more on:This package \|This alert \|What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at`support@socket.dev`. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment`@SocketSecurity ignore npm/vite@4.5.14`. You can also ignore all packages with`@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change thetriage state of this alert.