-
Notifications
You must be signed in to change notification settings - Fork 269
Open
Labels
Found:ManualTestsProduct:MCPServerThe Model Context Protocol (MCP) ServerThe Model Context Protocol (MCP) ServerType:BugWaitingForCustomerApplied when a NuGet triage person needs more info from the OPApplied when a NuGet triage person needs more info from the OP
Description
NuGet Product Used
Visual Studio Package Management UI
Product Version
VS Main\11625.112 + NuGet Client Dev\7.6.0.33
Worked before?
It's a regression since it doesn’t repro on VS Main\11617.104 + NuGet Client Dev\7.6.0.22.
Impact
It's more difficult to complete my work
Repro Steps & Context
Note:
- Repro rate: 100%
Repro Steps:
- Create a C# Console App (.NET 10.0) in VS and open the project-level PM UI.
- Go back to the ‘Browse’ tab of PM UI, select the source ‘nuget.org’ from the ‘Package source’ dropdown list and select a vulnerable package from the ‘Version’ dropdown list (for example, Newtonsoft.Json 11.0.2 in this instance).
- Install the vulnerable package and click the ‘Installed’ tab.
- Go to the Solution Explorer window and click the link ‘Fix with GitHub Copilot’ on vulnerability InfoBar at the top of Solution Explorer window.
- Click the ‘select tools’ button (the spanner icon) on the bottom-right of GitHub Copilot Chat window.
Expected Result:
No error occurs.
Actual Result:
NuGet MCP Server doesn’t work even after restarting as the screenshot below.
Verbose Logs
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Found:ManualTestsProduct:MCPServerThe Model Context Protocol (MCP) ServerThe Model Context Protocol (MCP) ServerType:BugWaitingForCustomerApplied when a NuGet triage person needs more info from the OPApplied when a NuGet triage person needs more info from the OP
Type
Fields
Give feedbackNo fields configured for issues without a type.