copilot-instructions.md documents `dotnet test` for server tests, which fails on .NET 10
维护者通常 2 天内回复
评估
- 难度
- 1/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 88/100
- Issue 类型
- 文档
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- csharp
调研方向
从 .github/copilot-instructions.md 第 60 行附近开始，验证 src/ServerTests 中记录的 server-test 命令。检查 ARCHITECTURE.md 或 README 是否重复了相同的说明，并与 CI 作业的测试调用进行比较。当面向贡献者的说明使用可正常工作的命令，且不再存在相互冲突的本地指导时，即表示完成。
由索引模型根据 Issue 内容生成。
描述
Problem
.github/copilot-instructions.md line 60 says:
- Run server tests:
dotnet testfrom theServerTestsproject.
That command no longer works. Running it in src/ServerTests fails before any test executes:
error : Testing with VSTest target is no longer supported by Microsoft.Testing.Platform
on .NET 10 SDK and later. If you use dotnet test, you should opt-in to the new dotnet test
experience. For more information, see https://aka.ms/dotnet-test-mtp-error
[src/ServerTests/ServerTests.csproj]
The project uses Microsoft.Testing.Platform, and under the .NET 10 SDK the VSTest target it routes through is gone.
What actually works
cd src/ServerTests
dotnet run
Test run summary: Passed! - src/ServerTests/bin/Debug/net10.0/ServerTests.dll (net10.0|x64)
total: 214
failed: 0
succeeded: 214
skipped: 0
Why this is worth fixing
The instructions file is the first thing an AI agent reads before touching this repo, and it is the documented entry point for contributors. A command that fails immediately sends the reader down a dead end at exactly the moment they are trying to verify their work.
The failure is also easy to misread. It surfaces as a red error : from an MSBuild target with a non-zero exit code, so it looks like a broken build or a failing test suite rather than a wrong command — the plausible next move is to start "fixing" code that was never broken.
This happened during a real session: the documented command was run against a green branch, failed, and needed a second attempt with dotnet run to discover all 214 tests actually pass.
Note CI is unaffected — the Unit Tests (Server/.NET) job passes, so it is invoking the suite some other way. Only the documented local command is wrong.
Suggested fix
Update line 60 to dotnet run, and ideally align it with however the CI job invokes the tests so the documented command and CI stay in agreement.
Worth checking whether ARCHITECTURE.md or the README repeat the same dotnet test instruction.
- 主要语言
- TypeScript
- 星标
- 6
- 派生
- 7
- 平均合并
- 3 天 5 小时
- 30 天内合并 PR
- 5
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
microsoft/Kusto-Explorer-VsCode 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
microsoft/Kusto-Explorer-VsCode#152 ·
维护者通常 2 天内回复
-
难度 4/5 3-5 天 新手友好度 68/100
microsoft/Kusto-Explorer-VsCode#158 ·
维护者通常 2 天内回复
-
enhancement
难度 4/5 3-5 天 新手友好度 68/100
microsoft/Kusto-Explorer-VsCode#151 ·
维护者通常 2 天内回复
-
Add a setting to scope the query CodeLens to the active query可能已有人在做 @AsafMah 于 66 天前认领。 未关闭enhancement
难度 4/5 3-5 天 新手友好度 68/100
microsoft/Kusto-Explorer-VsCode#141 ·
维护者通常 2 天内回复
-
Log Analytics / Application Insights connections truncate the full proxy URI to the bare hostname可能已有人在做 @AsafMah 于 66 天前认领。 未关闭bug
难度 3/5 1-2 天 新手友好度 55/100
microsoft/Kusto-Explorer-VsCode#139 · 1 条评论 · 1 个 reaction ·
维护者通常 2 天内回复
查看 microsoft/Kusto-Explorer-VsCode 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 83/100
appandflow/stim#5258 ·
维护者通常 1 天内回复
-
area/docs framework/hugo help wanted language/markdown
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
难度 1/5 1 小时以内 新手友好度 68/100
lingdojo/kana-dojo#33660 · 1 条评论 · 5 个 reaction ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
drizzle-team/drizzle-orm#6639 ·
维护者通常 4 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 76/100